4 ms·
I realized that Firefox 3.6 not supporting <aside> wouldn't really affect the layout, it's basically a <div> and it's floated left, something 3.6 can handle. Th
by extra88 10y ago
I realized that Firefox 3.6 not supporting <aside> wouldn't really affect the layout, it's basically a <div> and it's floated left, something 3.6 can handle. The main content has a class containing width: calc(100% - 250px); and Firefox didn't support calc() until 4 but that wouldn't explain it happening to you in 24.6 ESR.
Maybe older Firefox has a bug in calc(), disabling that property in a newer browser is enough to shift the content below the sidenav because it falls back to width: 100%;. I see what you mean about hard to read, if I disable the calc() width, the sidenav stays put but the main content scrolls on top of it. That's a little confusing because the sidenav staying put is due to the property position: sticky; but caniuse.com says Firefox didn't support that until version 26, version 32 without having to enable a flag.
Anyhow, I do think government guidelines in particular should handle older browsers better than this page is demonstrating. Part of the point of using frameworks for libraries and others is they can maintain and aggregate all the little solutions to problems between browser implementations and between older and newer browsers.
- wslack 10y agoThis is a really interesting question, given the very long tail of old browsers out there. There's downloadable data about the browsers visiting gov't websites (all anonymized by Google Analytics)[1], but that doesn't solve the "when do you stop supporting" question, particularly for old versions of IE. [1]: https://analytics.usa.gov/ https://analytics.usa.gov/