17091 2012-05-18 09:32:03 +0000 Step 25 - we (Opera) would prefer to follow WebKit and not add a new history position when doing document.open. The utility of this to users is questionable since many cases where it is used the content of the document before document.open is not useful ( 2012-07-18 18:39:15 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED DUPLICATE 17093 http://www.whatwg.org/specs/web-apps/current-work/#opening-the-input-stream P3 normal Unsorted 1 contributor ian james mike contributor oldest_to_newest 67828 0 contributor 2012-05-18 09:32:03 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#opening-the-input-stream Complete: http://www.whatwg.org/c#opening-the-input-stream Comment: Step 25 - we (Opera) would prefer to follow WebKit and not add a new history position when doing document.open. The utility of this to users is questionable since many cases where it is used the content of the document before document.open is not useful (e.g. it is a blank document) and other DOM operations can be just as destructive, but not create new history positions. In addition, any page that does document.open onload can leave the user in a situation where it is hard to navigate back past a given point in history because every time they load that page, an extra position is created. Posted from: 2001:4c28:a030:30:219:99ff:fe0e:5501 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.10.289 Version/12.00 67832 1 james 2012-05-18 09:36:21 +0000 *** This bug has been marked as a duplicate of bug 17093 ***