The “docked” class in the <body> tag is now always present, whereas it used to appear dynamically when scrolling started. adundovi finds this change problematic as the class loses its purpose and suggests reverting to the old behavior for custom header content display. Don provides alternative solutions from related topics on header scroll shadow and logo in docked header bar, noting that the mentioned .docked class is different from the one used for the .topic-progress-wrapper, which appears at the bottom of the topic when scrolled down. adundovi thanks Don for the suggestions and will investigate further.
It looks like something has changed recently in the way how Discourse handles the “docked” class in the <body> tag.
Before, if I remember correctly, “docked” appeared dynamically in <body> once the scrolling started (example), but now, it is always present. Now, unfortunately, this class loses its purpose: you could simply drop it completely and remove lines containnot(.docked). But it would be helpful to keep the old behaviour for us who still use it to display, for example, a different header content at the very top compared to the reduced header when user starts scrolling.
Is there another way how to handle the described case now? Please, advise.
