smaug----
smaug----
The problem is that for example removeNamedItem may return an Attr for the remove attribute even though some code run while the method was being executed an added another attribute...
Well, remove the the attribute using removeNamedItem, since with that you can actually see the side effect easily.
loading="idle" wouldn't probably work too well, since there is often plenty of idle time also during page load. (And I wouldn't want "idle" have different meaning with loading attribute) loading="domcontentloaded"...
I mean that if the loading of a "semi-lazy" image was triggered at domcontentloaded time, it would affect negatively loading of other resources.
I'm ok with https://github.com/whatwg/html/issues/2253#issuecomment-272150766 (though I still wonder if we're fixing any real world issue here or only theoretical issues. Need to be careful with adding more special cases; making...
pagehide isn't fired on tab switching. pagehide is like the better version of unload event.
We discussed with @petervanderbeken, and if possible would prefer reusing pagehide. It is after all not that different from (2) in case there are no redirects. And per spec page...
Why would there be async step between firing pagehide and marking page hidden. We can have a rendering step there if we want. (I'm not saying we should do that,...
I'm just saying that it would be possible, if we want that.
At which point would pagewillhide fire?