Open Bug 1751383 Opened 3 years ago Updated 3 months ago

Consider to support blocking="render"

Categories

(Core :: Layout, enhancement)

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.

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.

Blocks: html
Depends on: 1878888
Depends on: 1879074
Depends on: 1879340
Depends on: 1881598
Depends on: 1896150

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?

You need to log in before you can comment on or make changes to this bug.