Fix top calculations for paneled view
What does this MR do and why?
Many sticky elements calculate their top offset based on an assumption that they must take into account certain other sticky or fixed elements, like the performance bar, the top bar, and any admin banners. This is (happily) not true in the paneled layout, as these elements must only make themselves sticky relative to their parent panel and any sticky elements that should appear further up the page from them.
This can be easily achieved by setting the CSS variables for various element heights to 0px inside the panel, allowing for a baseline value of 0px that will have the heights of any other sticky elements added to it.
References
Screenshots or screen recordings
| Use case | Before | After |
|---|---|---|
| markdown preview sticky header in work item (fixed) |  |
 |
| markdown preview sticky header in MR (fixed) |  |
 |
| Incident sticky header and markdown preview sticky header on incident page (both fixed) |
|
 |
| todo bulk sticky header (no change but specific override code removed) |  |
 |
| work item sticky header (no change but specific override code removed) |  |
 |
| MR sticky header (no change but specific override code removed) |  |
 |
| MR file diff sticky header and MR file tree sticky element (no change but specific override code removed) |  |
 |
| Setting sticky header (no change but specific override code removed) |  |
 |
| Vulnerability dashboard (no change but specific override code removed) |  |
 |
How to set up and validate locally
- Check out this branch
- Ensure the paneled view is turned on
- Visit the pages in the screenshots above
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.