Query box cut off vertically
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript, react, redux
- Domain
- frontend
Research direction
Reproduce the issue by opening the site, selecting /me from the request dropdown, and checking the Query box in Safari or Chrome on mobile and desktop. Inspect the UI component and its layout styles to find why the populated properties are clipped; done means all query parameters are visible when sufficient screen space is available.
Written by the indexing model from the issue text.
Description
It appears that the Query box gets cut off prematurely regardless of screen size. Tested on mobile and desktop in Safari and Chrome.
To reproduce, open the site and then select /me from the request dropdown at the top. The query parameters should populate but won't all display despite having enough screen space available.
It would be nice to expand this box to accommodate the properties.
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Automattic/wp-api-console
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Automattic/wp-api-console#120 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Automattic/wp-api-console#119 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Automattic/wp-api-console#78 ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Automattic/wp-api-console#77 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Automattic/wp-api-console#67 ·
All issues in Automattic/wp-api-console
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
zmo2s/agent-toolbox#23 ·
-
[Bug]: [MCP/CLI] Bare loopback IP addresses (127.0.0.1:port) and hosts with ports fail to navigate due to erroneous scheme inferencePossibly taken @alok-108 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/playwright#43263 ·
Maintainers usually reply within 1 day
-
bug traffic
Difficulty 2/5 Under an hour Newbie friendliness 74/100