Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs

Dashboard
Notifications
Mark all as read
Q&A

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.

responsiveness 

+0
−2

Load codidact:

Codidact is loaded

Open menu:

Codidact menu is clicked

Grow window, menu opener disappears, but menu persists:

Codidact window is grown, menu opener disappeared, but menu persists

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (1 comment)

1 answer

+1
−0

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).

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!