- From: Jatinder Mann <jmann@microsoft.com>
- Date: Wed, 11 Apr 2012 16:26:01 +0000
- To: James Graham <jgraham@opera.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
> The term preview is used throughout the spec without really defining what it means. I have updated the spec with a definition of the term preview. > I don't think there is any need for vendor prefixed extensions here. In particular such prefixed >features have not been a successful model for extending the platform, with the prefixes themselves >becoming part of the defacto-required API. If we need to extend the API in the future with new use > cases we should do so in the spec rather than give people free reign to I agree that we should attempt to include as many visibilityStates as we can, however, I think there is value in allowing vendors to add experimental extensions. I have added "prerender" as an optional visibilityState to the spec based on this feedback. >In addition, the spec is contradictory. Section 4.2 defines in vague terms (but with normative language) >what should be returned in various situations. Then section 4.4 defines a processing model that explicitly >controls the value of the various attributes after specific actions. All the text from section 4.2 that is a >direct consequence of 4.4 should be made non-normative. The same applies to section 4.3. I have updated Section 4.2 to move all non-normative text to Notes. I have also capitalized the MUST and MAY clauses and clarified the text. I prefer the attribute definitions be normative. >In general please use formatting in a way that is consistent with other specs. Updated the formatting to be more consistent with other specs. >"Else if the user agent is to unload the Document contained by the top level browsing context, follow these steps, " > >Please use the hooks provided in HTML5 for this purpose. I have updated the processing model to include a hook into the HTML5 spec. I have also added an editorial note stating Issue-8 is tracking the issue of supporting the unloading/session history scenarios and this part of the spec has not yet been closed on. >"6 References" > >Please ensure that all urls are hyperlinks. Will do. Thanks, Jatinder
Received on Wednesday, 11 April 2012 16:26:36 UTC