We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buttons and Summary are in different stacking contexts. The impact is that no components in Summary can be in front of buttons, especially popins.
Put buttons and summary in the same stacking context. To do that, put them in a common div:
<HeaderScrolling> <div data-focus='sub-header'> <HeaderTopRow /> <HeaderActions /> </div> <HeaderContent /> </HeaderScrolling>
And set this common div as fixed with some z-index in data-deployed=false mode.
data-deployed=false
Focus-core: 2.1.1 Focus-components: 2.1.7-1
The text was updated successfully, but these errors were encountered:
@rodolpheV I agree, the whole header is messy for css stacks, position and so on. Problem is to avoid regression at the same time.
@c3dr0x Could you give it a try ? There is also the thing with expanded or not.
Sorry, something went wrong.
c3dr0x
No branches or pull requests
Current implementation
Buttons and Summary are in different stacking contexts. The impact is that no components in Summary can be in front of buttons, especially popins.
Expected implementation
Put buttons and summary in the same stacking context. To do that, put them in a common div:
And set this common div as fixed with some z-index in
data-deployed=false
mode.Versions
Focus-core: 2.1.1
Focus-components: 2.1.7-1
The text was updated successfully, but these errors were encountered: