RE: Page Visibility privacy section

>This contradicts the various "must" requirements listed throughout the specification. They should probably become "should" 
>requirements instead if there are indeed valid reasons not to follow them. Or the valid reasons are to be explicitly listed while 
>making the requirement, but then you need to be exhaustive.

I have removed the following non-normative text from the Privacy section:

"A User Agent may provide a setting to disable the Page Visibility API that when set will ensure the hidden attribute is set to false and the visibilityState attribute is set to visible."

> I also noticed that "must" is inconsistently cased throughout the specification and that the non-normative introduction section 
>contains a "must" requirement.



Received on Tuesday, 28 February 2012 21:55:18 UTC