- From: <bugzilla@jessica.w3.org>
- Date: Fri, 18 May 2012 09:35:42 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17093
Summary: 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 (
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#ope
ning-the-input-stream
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: other Hixie drafts (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org
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
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 18 May 2012 09:35:47 UTC