swagger-api / swagger-api/swagger-ui
No name property is assigned to "Server" Combobox.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: Windows 11 Enterprise - 23H2
- Browser: Edge
- Version: 124.0.2478.80 (Official build) (64-bit)
- Method of installation: npm
- Swagger-UI version: 4.6.1
- Swagger/OpenAPI version: Swagger 2.0, OpenAPI(2,3)
Content & configuration
Example Swagger/OpenAPI definition:
# your YAML here
Swagger-UI configuration options:
SwaggerUI({
// your config options here
})
?yourQueryStringConfig
Describe the bug you're encountering
To reproduce...
Steps to reproduce the behavior:
- Launch the URL : https://codesandbox.io/p/sandbox/swagger-ui-forked-kcm88z?file=%2fpackage.json%3A7%2C20
- TAB till "Sever" Combobox.
- Observe that name property is defined for the Combobox or not.
Actual result
No name property is assigned to "Server" Combobox.
Expected behavior
Correct Name property should be assigned to "Server" Combobox.
Screenshots
Additional context or thoughts
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CodeSandbox reproduction and inspect the Server Combobox shown after tabbing to it. Add the correct accessible name property, then verify that the combobox exposes that name in the reproduction and does not regress related behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100