Simon Pieters
Simon Pieters
@achristensen07's objection in https://github.com/whatwg/url/pull/284#issuecomment-303833495 as I understand it was mainly: > Our URL object is used for many things in the operating system that have nothing to do with HTML...
I've discussed this with @mozfreddyb and @valenting. We're OK with this PR. I still think the added fragmentation of different behavior for different URL entry points in the web platform...
I found an existing WebKit bug (https://bugs.webkit.org/show_bug.cgi?id=172748). I think this is ready to merge, but leaving to @annevk.
This seems OK. Gecko also uses `:any-link`: https://searchfox.org/mozilla-central/source/layout/style/res/ua.css#151
It's not observable to web content.
Why isn't using only eager images (maybe with `fetchpriority="low"` on ones below the fold) sufficient?
I'm told fetchpriority can also be a signal to the browser for e.g. resource allocation and quotas for parallel fetches. Still, I accept that network congestion can happen even with...
The legacy HTML fragment parser APIs don't support DSD and don't have Sanitizer API support. They also parse as HTML or XML depending on the "[HTML document](https://dom.spec.whatwg.org/#html-document)" bit on the...
The parser can close these elements without their end tag sooner than The End. But adding a flag when it happens seems doable...
No, that can be bypassed with `novalidate`.