4 ms·
Since obsolete unterbrowser users must suffer, rem FTW. What's REALLY missing in modern CSS3 standard is the ability to reassign CSS root to any other element
by plugnburn 11y ago
Since obsolete unterbrowser users must suffer, rem FTW.
What's REALLY missing in modern CSS3 standard is the ability to reassign CSS root to any other element than <html>, according to font properties of which all nested rems would be calculated. So, for now, we have to stick to assigning base font sizes to <html>, not even to <body>.
My microframework (999.css - http://999.surge.sh http://999.surge.sh) uses pixels to assign base font size to <html>, rem for <body>, ems for headings and rems for all other nested typography.
- err4nt 11y agoWhile I don't have a solution that lets you reassign the CSS root to other elements, I do use a plugin in my own work that lets me use scoped styles, as well as element queries. It solves a lot of problems. You should check it out, the learning curve is small, and it is even supported well in unterbrowsers: http://elementqueries.com http://elementqueries.com
- plugnburn 11y agoI would love to check it out, if only your page didn't hang my Firefox. It's really impossible to scroll. Lags are ~10-15s. Hardly even closed the tab. What's going on there? Was it really written with performance in mind? :)
- err4nt 11y agoYeah, I'm not the JS dev, but the issue is known and being looked into. Strangely it didn't affect previous versions of Firefox and whatever is broken at the moment is already fixed in upcoming beta versions of Firefox. I'm not sure what or why, but it might become fixed from mozillas end before a workaround gets diagnosed. How does it work in IE8 and previous Firefox, but have issues with the current build, but not with upcoming builds? It baffles me