You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
I was wondering whether the new renderPriority attribute will have effects on iframes (either because it is set on the iframe element itself or because it is inherited from an ancestor element). If so, could this have security/privacy implications? By assigning different renderPriority to different iframes, you could get rendering timing information about a (possibly cross-origin) iframe.
The text was updated successfully, but these errors were encountered:
I think this is a fair point. My initial thoughts is that we would either allow rendering to happen in iframes or we wouldn't. I don't think we would be able to enforce something like background priority for iframes (especially cross origin)
I think we should definitely let renderPriority affect iframes, since some content needs to be put in iframes and it's still a legitimate use case to pre-render iframe content.
That being said, we should work carefully through appropriate mitigations for priviacy and security as necessary.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was wondering whether the new
renderPriority
attribute will have effects on iframes (either because it is set on the iframe element itself or because it is inherited from an ancestor element). If so, could this have security/privacy implications? By assigning differentrenderPriority
to different iframes, you could get rendering timing information about a (possibly cross-origin) iframe.The text was updated successfully, but these errors were encountered: