> On 24 Jul 2018, at 01:36, Tanushree Podder <tpod...@mozilla.com> wrote: > > Summary: Mobile web pages contain two viewports, the layout viewport and > the visual viewport. The layout viewport consists of all the page contents > and is specified by the meta-viewport tag. The visual viewport is the > actual visible portion of the page on the screen excluding on-screen > keyboards, areas outside of a pinch-zoom area or any other on-screen > artifact that does not scale with the dimensions of the page. The purpose > of the Visual Viewport API is to allow web developers to explicitly query > the properties of the visual viewport. > > Web developers can use this API in situations where they need to position > web page elements to remain visible on the screen regardless of the visible > portion of the web page. For example, if an image needs to be visible > regardless of the pinch-zoom level of the device, it can be positioned > relative to what’s shown on the screen using methods of the Visual Viewport > API.
About the desktop perspective: is pinch-to-zoom a completely separate thing from full-page-zoom as can be controlled right now with Ctrl+ and Ctrl- using the keyboard? If that’s the case, I can see synchronization issues between the two features when they’re both in use. My perception is that pinch-to-zoom is really full-page-zoom, but using the pointer coordinates as focal point instead of [0,0] and step-less zooming behaviour, instead of clamping to predefined steps. If that’s not the case, I’d say the new API seems usable on desktop already once the page has been zoomed in. Thanks, Mike. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
