You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing the application on mobile or tablet, if a user opens a megadropdown within the PostHeader and then resizes the window to desktop size before resizing back down to a mobile/tablet size, the megadropdown's positioning is incorrect.
When a user opens a megadropdown in desktop size, then the resizes the window to a tablet/mobile breakpoint (which closes the megadropdown), and subsequently opens the mobile menu, the megadropdown retains its previous expanded state from the desktop view.
🛠️ To Reproduce
Steps to reproduce the behavior:
Set the browser viewport size to a mobile/tablet.
Interact with the PostHeader to open a megadropdown.
Resize the browser window to a desktop size.
Resize the browser window back down to a mobile/tablet size.
Observe the position of the megadropdown.
✨ Expected behavior
When resizing back from desktop to table breakpoint, the megadropdown should be closed and if opened again it should be correctly positioned for the mobile/tablet layout, starting from the bottom of the header.
When the mobile menu is opened after the resize from desktop, all nested menus (like megadropdowns) should be in their default, collapsed state.
📷 Screenshots
💻 Desktop
Browser: Edge/Safari
The text was updated successfully, but these errors were encountered:
myrta2302
changed the title
[bug]: PostHeader: Megadropdown position and menu state after resize
[bug]: Post Header - megadropdown position and menu after resize
May 19, 2025
Uh oh!
There was an error while loading. Please reload this page.
🐞 Describe the bug
This is probably addressed by this PR: #5490
🛠️ To Reproduce
Steps to reproduce the behavior:
✨ Expected behavior
📷 Screenshots
💻 Desktop
The text was updated successfully, but these errors were encountered: