Open dwrensha opened 9 years ago
AFAICT this is a bug in Chrome. There is no javascript executing -- everything is CSS-based -- so resizing should have no side-effects. I'm not sure what to do about it, but I think this is probably rare to see in regular usage.
FWIW I see this consistently now.
:heart: !
Chromium claims to have fixed this: https://code.google.com/p/chromium/issues/detail?id=411256, but I'm still seeing the bad behavior, as of Chrome Version 46.0.2490.80.
I still see this problem in my Debian chromium: 46.0.2490.71-1
But in a Chrome dev channel build, it seems fixed. Partial version details from chrome://version/
Google Chrome 48.0.2547.0 (Official Build) dev (64-bit)
Revision 625f6c8cd6bda5cd7a5b1691376956bb8f300785-refs/heads/master@{#356202}
OS Linux
Blink 537.36 (@625f6c8cd6bda5cd7a5b1691376956bb8f300785)
This also happens in Safari, fwiw.
Oh man. If it also happens in Safari, then our current strategy of "Wait for everyone to auto-update to a non-broken Chrome build" is probably not going to cut it.
I swear I tested this in safari at the time...
Fascinatingly if I uncheck float: right;
within the CSS of the affected elements, and then check that box, the elements figure out where to put themselves. Specifically I unchecked:
@media (min-width: 901px)
body > .topbar > .menubar > .account {
float: right;
and
@media (min-width: 901px)
body > .topbar > .menubar > .notifications {
float: right;
within the Chromium DOM inspector, then checked the boxes again, and they figure out what to do.
I can reproduce this in Safari "Version 9.0.1 (10601.2.7.2)". It seems to only happen when a grain is currently open and being viewed. For example, if you are at /apps then you can resize the window without any problems.
Can we close this issue now or is it still persisting?
Yeah this chrome issue is long-gone.
Reopening; had a verbal report of this issue in Webkit from someone at the meetup last night.
We should switch to using flexbox for the menubar.
Still appears to be broken in Safari for me. :( Version 9.0.3 (11601.4.4)
Still a problem in Safari 10.0.
I see this behavior in Chrome but not Firefox.