- From: Jatinder Mann <jmann@microsoft.com>
- Date: Fri, 22 Jun 2012 21:21:58 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>, "Karen Anderson (IE)" <Karen.Anderson@microsoft.com>
- CC: Carl-Anton Ingmarsson <carlantoni@opera.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
In the case of dynamic markup insertion, I agree with Karen that it is confusing to update some of the attributes and not the others, particularly because the timeline implies an ordering. Our options appear to either not allow dynamic markup insertion to change the Navigation Timing attributes or in the dynamic markup insertion case, to update all attributes, including zero deltas for attributes that are not changed. It appears that the spec authors attempted to capture the former, though the spec text is not very clear. I recommend we fix the spec bug to make the intended behavior more clear. What are your thoughts on this proposed text: 1.If the navigation or document is aborted for any of the following reasons, abort these steps without changing the attributes in window.performance.timing and window.performance.navigation. a. The navigation is aborted due to the sandboxed navigation browsing context flag or the sandboxed top-level navigation browsing context flag, or a preexist attempt to navigate the browsing context. b. The navigation is caused by fragment identifiers within the page. c. The document is replaced in-place by dynamic markup insertion. (link to http://www.w3.org/TR/html5/dynamic-markup-insertion.html#dom-document-open) d. The new resource is to be handled using a mechanism that does not affect the browsing context. e. The user refuses to allow the document to be unloaded. Do you think this change is sufficient to make it clear that document.open/.write./.close will not change the performance.timing and performance.navigation attribute values? Thanks, Jatinder
Received on Friday, 22 June 2012 21:22:43 UTC