- From: Jatinder Mann <jmann@microsoft.com>
- Date: Thu, 28 Jun 2012 02:20:53 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: "Karen Anderson (IE)" <Karen.Anderson@microsoft.com>, Carl-Anton Ingmarsson <carlantoni@opera.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On Saturday, June 23, 2012 10:26 PM, Boris Zbarsky wrote: > In Gecko, at least, what makes something a "navigation" is whether certain events > fire and whether the Window object changes. Document object identity never even > enters the picture. Since this specification does not define what a "navigation" is, > Gecko is simply using its internal definition, and as far as I can tell that's perfectly > conformant with the spec as it is written now. > > If the intent of the spec is to exclude document.open from changing the state, then > the specification needs to define "navigation" accordingly. I agree that the specification should explicitly define "navigation". Aside from excluding dynamic markup insertion, it is something the spec should have nonetheless. I will propose some text shortly and solicit feedback. Thanks, Jatinder
Received on Thursday, 28 June 2012 02:21:32 UTC