Re: [csswg-drafts] [cssom-view] layout viewport vs visual viewport

Re: the change in Blink/WebKit, I'm not sure I necessarily agree with pinch-zoom only being an accessibility feature, or that transparency to the web platform is the correct default as a blanket statement.  I think it's highly situational to the intended usage of the API in question, e.g. the IntersectionObserver API where "on-screen visibility" is the motivating use case of the feature (see discussion in [this issue](https://github.com/WICG/IntersectionObserver/issues/95)).  I do agree that the specific list David provided in his document all could make sense referring to the layout viewport.

If you are making another run at this change, then I take it you feel the [developer feedback](https://bugs.chromium.org/p/chromium/issues/detail?id=571297) has been adequately addressed by the addition of the VisualViewport API?

Re: terminology, I think using the term "layout viewport" is clearer to read and makes it more obvious whether a spec intends to refer to the layout/visual viewport vs. is ignorant of the difference.  I don't have a particularly strong opinion but it does seem to encourage ambiguity to leave off "layout".

Even if we do settle on just "viewport" there is still language that needs updating, e.g. the [definition of "viewport"](http://www.w3.org/TR/CSS2/visuren.html#viewport) still refers to it both as a "viewing area" and influencing the layout, making it unclear whether it's referring to the visual viewport or the layout viewport.

-- 
GitHub Notification of comment by ChumpChief
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/505#issuecomment-295363614 using your GitHub account

Received on Wednesday, 19 April 2017 17:47:18 UTC