Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
I don't think it's feasible to support browser-width changes in the header dropout component. That's mostly for two reasons: The same code is used for multiple elements, including the menu, t...
Answer
#1: Initial revision
by
luap42
·
2021-03-27T16:23:46Z (over 3 years ago)
I don't think it's feasible to support browser-width changes in the header dropout component. That's mostly for two reasons: 1. The same code is used for multiple elements, including the menu, the search bar and the inbox. Because - for example - the latter two are also enabled on desktop screen sizes, we can't just hide all those dialogs on large screens. 2. These components are positioned relative to the trigger element, *the moment it is clicked*. While the position is good for one specific screen size, it may look catastrophically on any other screen size. We can't really adopt to that, because then we'd need to track the resize of the window. While there is a `resize` event, there doesn't seem to be a `resize end` event, requiring us to recalculate the position and to redraw the component every cycle the event triggers. This is probably going to be quite an expensive operation, possibly causing your browser to slow down. (I didn't try that one yet, but AFAIK there are issues with `scroll`, which looks similiar on the first sight).