#66030 closed defect (bug) (duplicate)
Admin toolbar layout overlap blocks "Help" toggle click event at 783px–894px viewports
| Reported by: | saiful09 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Toolbar | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | ui |
Description
A responsive layout bug occurs in the WordPress administration dashboard when the viewport width is between 783px and 894px.
Within this specific breakpoint range, components within the top admin bar overlap the Help tab toggle. Due to this layout collision, the underlying interactive element is obscured, rendering the click event for the Help drawer completely unresponsive.
Steps to Reproduce
- Log into the WordPress dashboard.
- Resize the browser window or use responsive design tools to set the viewport width between 783px and 894px.
- Navigate to the top-right toolbar area beside the "Screen Options" tab.
- Attempt to click the Help toggle button.
Expected Behavior
The Help toggle button should remain fully visible, properly spaced, and clickable at all responsive viewport widths without interference from adjacent admin toolbar elements.
Actual Behavior
The admin info/metrics element overlaps the Help toggle, intercepting pointer events and preventing the Help panel from opening.
Attachments (1)
Change History (4)
#2
@
5 weeks ago
- Component Help/About → Toolbar
- Focuses ui added
- Milestone Awaiting Review
- Resolution → duplicate
- Status new → closed
Duplicate of #28983.
I think the issue reported here is essentially that the toolbar wrapping is not handled properly.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hi @saiful09, thanks for reporting this!
I tried reproducing the layout overlap at the 783px–894px breakpoints using WordPress Playground, but the Help toggle remained accessible and clickable on my end.
Could you please check if you can still reproduce this in a fresh WordPress Playground instance, or confirm if it still occurs on your setup with all plugins disabled and a default theme active? This will help us narrow down whether it is a core responsive issue or a potential conflict.
Video: https://rioudcpuyg.ufs.sh/f/PL8E4NiPUWyOrX6MaOltMk7y2dfFYKmqLWZt4AHpRVDaCBls