Consider to support blocking="render"
Categories
(Core :: Layout, enhancement)
Tracking
()
People
(Reporter: smaug, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, parity-chrome)
https://github.com/whatwg/html/issues/7131
https://github.com/mozilla/standards-positions/issues/608
We need to be careful to not cause some new security/privacy issues by letting the page to block rendering forever. The current PR does let UA to unblock rendering after a timeout.
The might be other kinks in the proposal too.
Comment 1•10 months ago
|
||
Also for inline scripts: https://github.com/whatwg/html/pull/10035
Usage is still low, but seems to be increasing: https://chromestatus.com/metrics/feature/timeline/popularity/4183 currently 0.03% of page loads.
Updated•10 months ago
|
Usage is still low, but seems to be increasing: https://chromestatus.com/metrics/feature/timeline/popularity/4183 currently 0.03% of page loads.
I assume the usage is low because it's not cross-browser supported.
Currently, the usage is at ~0.1%. What is the threshold to start developing the feature?
Comment hidden (metoo) |
Updated•3 months ago
|
Description
•