Postponed
Project:
Drupal core
Version:
main
Component:
Olivero theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 Apr 2021 at 14:43 UTC
Updated:
19 Aug 2026 at 10:21 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
aaronmchaleI mentioned during #3208186: Drupal Usability Meeting 2021-04-23 while we discussed the implementation in #3190120: Olivero: Focused level-2 nav items should always be in viewport during keyboard navigation. that I thought there was a way to essentially stop the browser from scrolling when the menu is open.
The method I have used to accomplish this in the past is, by applying
overflow: hiddento thehtmltag when the menu is open, this temporarily removes the browsers scroll bars and so freezes the position of the browser. This might be possible using CSS selectors, I couldn't find the exact code I had used in the past.The result of this would be that when the user has the menu open, if they scroll to the bottom of the menu, their browser would not continue to scroll the page and so they would not inadvertently close the menu.
Comment #4
mherchelComment #5
mherchelThis solves the issue. Needs tests though.
Comment #6
gauravvvv commentedThis is fixed, Tested patch #5, If the menu item has focus then header is not collapsing.
Added after patch screen recording.
Moving to RTBC
Comment #7
gauravvvv commentedIf we scroll the window while menu item has focus then header is not closing, which is perfect as per issue. but if try this once then move focus to page title or any other component/element of the page and we scroll then header is not closing itself. it's an issue. this should be fixed.
Moving to NW.
Comment #8
kiran.kadam911Thanks @mherchel for the patch. Providing updated patch to resolve issue mentioned in #7 by @Gauravmahlawat
A screencast is attached for reference. Kindly review the attached patch.
Thanks!
Comment #9
xjmAs an accessibility issue, this is at least normal and possibly major.
Comment #10
chetanbharambe commentedVerified and tested patch #8.
Patch applied successfully and looks good to me.
Testing Steps:
# Goto: Appearance:- Set Olivero theme
# Create sub-menu under any main navigation menu
# Tab into the primary menu and open a submenu
# Scroll down the page.
# Note that the header menu will collapse.
Expected Results:
# Header menu should not collapse when the user evaluating accessibility while pressing the tab key.
Actual Results:
# Header menu is collapsing when the user evaluating accessibility while pressing the tab key.
Please refer attached videos.
Looks good to me.
Can be a move to RTBC.
Comment #11
mherchelLooks like the tests aren't passing.
Comment #12
sagarchauhan commentedFixed the patch for failing test and retaining the behaviour of header being still visible in case there is focus on any of its children. Added a screenshot to show the behaviour after the patch.
Comment #13
sagarchauhan commentedAdded a wrong patch. Updating with the right patch and interdiff. The comment and the screencast is same as #12.
Comment #15
sagarchauhan commentedComment #16
heni_deepak commented#13 Patch applied. Please check the report video.
Report
1. patch has a fixed menu if focuses on the submenu.
2. Menu forgot his basic behavior after testing 1 point.
3. When I click on the left side menu toggle button. the basic behavior comes back.
Comment #20
pradipmodh13 commentedIn Drupal 10.1.x Header menu is not closing if menu item has focus. It is working fine as expected.
We can move this bug to RTBC.
Comment #21
andy-blumThe recording in #20 is deceptive. While that's the behavior we're aiming for, we need it to occur automatically. If a user hasn't already scrolled down and opened the header, this behavior does not occur. Patch #13 is pretty out-dated at this point and will need a reroll.
Comment #22
_utsavsharma commentedTried to re-roll for 10.1.x.
Please review.
Comment #23
Bushra Shaikh commentedI have applied patch #22 on drupal 10.1.x version. Patch failed.
Comment #24
mgiffordYes, that could be a failure of a few SC https://www.w3.org/WAI/WCAG21/Techniques/failures/F55
Just tagging it for 2.1.1.
Comment #25
gauravvvv commentedUpdating attributions.
Comment #26
smustgrave commentedStill needs a test case from what I can see.
Comment #29
quietone commentedThe Olivero theme was approved for removal in #3590816: [policy, no patch] Deprecate Olivero and move to contrib.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3595082: [meta] Tasks to deprecate the Olivero theme and the removal work in #3595085: [meta] Tasks to remove the Olivero theme.
Comment #30
quietone commented