W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2009

[Bug 7418] New: See if we can make popstate more synchronous so that when it fires, the doc is in the expected state, rather than three back-button-steps later. But consider nested calls to history.back().

From: <bugzilla@wiggum.w3.org>
Date: Tue, 25 Aug 2009 03:30:40 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-7418-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7418

           Summary: See if we can make popstate more synchronous so that
                    when it fires, the doc is in the expected state, rather
                    than three back-button-steps later. But consider nested
                    calls to history.back().
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://whatwg.org/specs/web-apps/current-work/#event-
                    popstate
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Section: http://whatwg.org/specs/web-apps/current-work/#event-popstate

Comment:
See if we can make popstate more synchronous so that when it fires, the doc is
in the expected state, rather than three back-button-steps later. But consider
nested calls to history.back().

Posted from: 69.228.190.230


-- 
Configure bugmail: http://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 Tuesday, 25 August 2009 03:30:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 August 2009 03:31:00 GMT