RE: [Page Visibility] Navigate away behavior (was RE: TPAC 2011 Web Performance WG 2011-11-01)

> 1) When traversing _from_ session history entries browsers fire a _pagehide_ 
> event.  But your spec text talks about firing a _pageshow_ event.  There's a 
> similar issue with the events being reversed in teh traversing _to_ session 
> history entries case.

I had a feeling I had that backwards. I will make the update.

> 2) When unloading a document, why would a UA not end up in the " Else if 
> the Document contained by the top level browsing context is now not visible" 
> branch if the if/else cascade?  Seems like it would, as the spec is currently written...

I can incorporate the unloading steps as a part of the "now not visible" else if statement.

> 3) The addition of pageshow/pagehide event firing in this spec would, if actually 
> implemented, make those events fire twice.  That doesn't seem right.

That's a good point. Do you know which HTML5 spec hooks I should reference?

> 4) The event firing for the "unloading document visibility change steps" 
> should not be restricted to the unloading of top-level documents, imo: 
> if a subframe document is unloaded its visibility should change to hidden.

As we had previously discussed, we wanted to limit iframe visibility to match that of the top level browsing context in this version of the spec and possibly consider more detailed iframe visibility in a future version of the spec. For consistency, I think the unload behavior should also continue to be tied to the top level document until we fully incorporate the detailed iframe visibility in the next version, including things like scrolling iframes out of the viewport, etc.


Received on Tuesday, 22 May 2012 17:38:26 UTC