- From: Jatinder Mann <jmann@microsoft.com>
- Date: Wed, 10 Aug 2011 21:01:46 +0000
- To: timeless <timeless@gmail.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Thank you for your feedback. I have gone ahead and made all the grammar, spelling and markup changes you had suggested in the latest Editor's Draft - http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html. I have also made the specification clear that a User Agent must only define the document.PAGE_PREVIEW constant if it is supporting the optional behavior. As for the concern around using the word "screen", this word appears to be used commonly without a normative definition, like in http://www.w3.org/TR/CSS2/media.html. I am not as familiar with voice based browsers. How would visibility play a role in such a browser? Recall that visibility is not the same as focused. Some members, including myself, had concerns with the technical feasibility of determining visibility for the case where a browser isn't minimized but is fully obscured by other applications. We have designed the spec to fallback to visible when in doubt, rather than falling back to hidden. The example of a Magnifying application that may fully obscure the browser but still allow a user to visibly view the contents is an example of where this behavior is useful. Thanks, Jatinder
Received on Wednesday, 10 August 2011 21:02:16 UTC