> <i>New viewport units</i><p>These new viewport units frustrate me immensely, because they have completely ignored the longstanding complete brokenness of viewport units on platforms that don’t use zero-layout-width overlay scrollbars (which currently means pretty much all desktop platforms except macOS by default, and even there it’s at least easily possible to turn off overlay scrollbars). Basically, viewport units are <i>always</i> the wrong thing if there might be scrollbars: they’re broken by design.<p>Instead they’ve fixed the problem with inconsistency of interpretation of viewport <i>height</i> units on <i>mobile</i> browsers, which was, generally speaking, not something that was <i>broken</i> in the same way as the desktop situation, and there were simple (if non-obvious) practical workarounds for the most likely thing people wanted anyway.<p>So yeah, the new viewport units <i>are</i> worthwhile for what they improve in mobile browsers, but I’m disgruntled that they’re being presented as fixing viewport unit situation when the people involved have continued to basically ignore what I perceive as the <i>real</i> and most significant problem with viewport units, which has been an issue from the very start in all browsers except Firefox, which <i>used</i> to have a tolerable workaround (essentially: `body { overflow-y: scroll }` would make vw exclude the scrollbar) until it was ripped out of the spec and Firefox because no one else was interested in implementing it for some reason.<p>In short: the new viewport units are <i>still</i> fundamentally broken by design, only in a way that doesn’t affect most mobile platforms or the default macOS configuration.
Funny that the subgrid example actually has a screenshot from a browser that doesn't support subgrid: <a href="https://github.com/GoogleChrome/web.dev/issues/7453" rel="nofollow">https://github.com/GoogleChrome/web.dev/issues/7453</a><p>Well, that does say something about the dominance of Chrome...
The last feature vanilla CSS needs to render most pre-processors obsolete (imo) is nesting. The latest CSS nesting specs are looking great and it's kinda sad to not see it being prioritized
I'm absolutely horrified at what the "modern web" has become. More complexity, more bugs, more barriers to entry for anyone else wanting to write their own browser and have it be usable for most sites. Google seems determined to squeeze everyone else out with this feature-churn.
We used to have ACID 2 and ACID 3, do we have something similar to ACID 4? Or at least a subset of features that are <i>guarantee</i> to work across all browsers. While Caniuse is useful for checking support, many times there are browser that support something but it is buggy or differ from one another.
Shouldn't it be "to improve the web for <i>users</i>" ? Developer Experience is important, but it shouldn't be focused on in isolation from User Experience. If we were just talking about improving an IDE, it's fine, but "the web" is about much more than development.<p>Personally I think the way web browsers work is kind of insane from a user perspective. "The Web" is obsessed with technical expertise and custom code. An application like MS PowerPoint (pick any other design tool you prefer) is designed for <i>users</i> to create multi-layered media content and display it anywhere, without requiring a college degree or months/years of experience to make something. I don't think people who actively work on the web have considered how over-complicated it all is. For an industry that talks obsessively about "innovation" and "disruption", it can't seem to conceive of a post-web-browser world.
It's been a while since I looked into it, but are storage limits still a pain to handle across browsers?<p>According to this article, Safari doesn't yet have properly documented limits on storage.<p><a href="https://web.dev/storage-for-the-web/" rel="nofollow">https://web.dev/storage-for-the-web/</a>
I’m impressed safari is at the table. If I understand correctly, they only fix bugs once every six months, and don’t give any indication of timelines as matter of policy. For example, hasn’t locaStorage been broken in safari for ages? Or am I a bit behind the times? (Would have hoped to see that on the list if so)