You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every once in a while (maybe 1 in 10 page loads) the "Download" button is partially obscured (but still works):
It's basically a less-severe version of #63 and the long term fix is the same, which is either to eliminate the instability in the page layout (i.e., things jumping around as content and/or CSS loads) or ensure that the affected elements are loaded/displayed/positioned until after everything else has loaded and the layout has stabilized. I believe the Chaise/Navbar team is looking at making sure that their Chaise-specific CSS doesn't inadvertently conflict with other directives on the page, in case that is contributing to the problem. We may need to simplify the page layout (fewer flex boxes if possible) and/or look more carefully at the order in which CSS and content files are loaded.
The text was updated successfully, but these errors were encountered:
I believe I've fixed the layout thrashing (at least in the horizontal dimension) that was giving rise to this bug. It was committed today and I assume it will show up in app-dev tomorrow so we can test it out. I've also made some improvements to the responsiveness of the landing page, but I'll discuss those over in #79.
Every once in a while (maybe 1 in 10 page loads) the "Download" button is partially obscured (but still works):
It's basically a less-severe version of #63 and the long term fix is the same, which is either to eliminate the instability in the page layout (i.e., things jumping around as content and/or CSS loads) or ensure that the affected elements are loaded/displayed/positioned until after everything else has loaded and the layout has stabilized. I believe the Chaise/Navbar team is looking at making sure that their Chaise-specific CSS doesn't inadvertently conflict with other directives on the page, in case that is contributing to the problem. We may need to simplify the page layout (fewer flex boxes if possible) and/or look more carefully at the order in which CSS and content files are loaded.
The text was updated successfully, but these errors were encountered: