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
The spec does not mention if the Visual Viewport API is restricted to secure contexts only. Currently, in Chrome the Visual Viewport API is available in non-secure contexts. The W3C spec for secure contexts https://w3c.github.io/webappsec-secure-contexts/#new recommends all new features to be restricted to secure contexts. For existing features which are not widely used but widely implemented, the spec suggests applying this restriction and modifying the specs of the existing feature. What do you think about restricting the Visual Viewport API to secure contexts?
The text was updated successfully, but these errors were encountered:
The link you provide specifically mentions sensitive APIs which I would assume are those that can have privacy or other adverse consequences. I would assume VisualViewport is more akin to basic geometry information about the page (e.g. like window.innerWidth/Height) so I don't really see a reason it would need to be restricted - did this come up in a particular use case or example?
I think we overlooked the fact that the linked policy only applies to sensitive APIs (which I agree Visual Viewport is not). I think part of the confusion is that for new APIs, we are trying to restrict everything (sensitive or not) to secure contexts.
Yeah, that sounds fine to me. Unfortunately, we've been shipping it like this for a while so there's a non-trivial number of uses - I'll have to do some investigation to see if that's practical to do.
The spec does not mention if the Visual Viewport API is restricted to secure contexts only. Currently, in Chrome the Visual Viewport API is available in non-secure contexts. The W3C spec for secure contexts https://w3c.github.io/webappsec-secure-contexts/#new recommends all new features to be restricted to secure contexts. For existing features which are not widely used but widely implemented, the spec suggests applying this restriction and modifying the specs of the existing feature. What do you think about restricting the Visual Viewport API to secure contexts?
The text was updated successfully, but these errors were encountered: