[Minor] Issue with archived pages, top bar is missing z-index
See original GitHub issue- Set the screen resolution to 1920x1080
- Go to https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Scroll-linked_effects (or any other page using this banner)
- Observe the archived page bar
Expected:
I expected the top bar to be in the middle
Actual:
The text in the top bar is shifted to the right
Fix
Add left: 0;
to .archived {
in the css file index.scss
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
[Solved] Safari for iOS: z-index order bug scrolling a page with ...
I do so by making sure that the z-index of the menu button is lower than the one from the header, and everything...
Read more >4 reasons your z-index isn't working (and how to fix it)
Solution: Move the modal outside of the content parent, and into the main stacking context of the page. The corrected markup would then...
Read more >I am having a z-index dropdown issue - Stack Overflow
Your dropdown menu getting disappear because it is not having any connection with your parent element.
Read more >My Widget Is Being Covered Up By Something Else - Elementor
If one element is on top of, or under, another element, and the positions should be reversed, you need to change the Z-index...
Read more >z-index of top bar - WordPress.org
By adding the below CSS code, you can change the Z-index value for the top bar as per your need. #site-header.medium-header .top-header-wrap {...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No fix necessary. These pages will be deleted off MDN first week of July this year. And I don’t want to close it until that has officially happened.
Thank you so much for thinking about a fix.
Besides, one thing we can, today already (but perhaps merge it a little bit later), do is find if that banner has any (S)CSS that we can now delete because it’s going to just be an orphan that can never be used again.
It looks there there was some scss associated with the
.archived
class for that top bar, I did a quickgit grep
search, the.archived {}
scss declaration is only being used once:and here is the corresponding scss within
client/src/document/client/index.scss
plus the
<div>
element that represents that archived bar in HTML:I assume since the class
.archived
is no longer going to be used in the className declaration in JSX, then we can probably go ahead and remove that entire<div>
along with the scss. Submitting a PR shortly and we can hold off on merging until ready.