New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blocking="render" attribute on <link>, <script> and <style> #608
Comments
Well, UA can always stop the blocking. Otherwise there would be security/privacy issues. I think in general the idea is quite reasonable. |
@smaug---- can you clarify the question. Did you mean the impact of resizing the window? As per the spec text here there's no rendering opportunities while we're blocked. So no events which happen during the rendering lifecycle run. |
Intending to amend the current spec for render-blocking scripts to also include inline scripts, see whatwg/html#10035 |
I think this is reasonable and useful. My main concern is that it might be a bit too easy to block rendering on a |
Filed whatwg/html#10068 I think that issue can be resolved without changes to how the feature works. Suggest |
Request for Mozilla Position on an Emerging Web Specification
blocking="render"
attribute on<link>
,<script>
and<style>
blocking="render"
attribute on <link>, <script> and <style> whatwg/html#7131Other information
This proposal also includes the standardization of a general render-blocking mechanism, which will standardize the existing stylesheet loading behaviors and support the proposed attribute. The proposed behavior slightly differs from Firefox's current behavior: the proposal does not allow
requestAnimationFrame()
callbacks to fire until all render-blocking stylesheets are loaded, while Firefox currently allows it.The text was updated successfully, but these errors were encountered: