[Bug 9193] New: "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9193

           Summary: "If hash changed is true, then, if the new URL has a
                    fragment identifier, scroll to the fragment identifier."
                    is wrong. It should scroll if it's a new entry that
                    hasn't been traversed to before, even if it's the same
                    fragid as before; and it should _not_
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-
                    work/#history-traversal
        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://www.whatwg.org/specs/web-apps/current-work/#history-traversal

Comment:
"If hash changed is true, then, if the new URL has a fragment identifier,
scroll to the fragment identifier." is wrong. It should scroll if it's a new
entry that hasn't been traversed to before, even if it's the same fragid as
before; and it should _not_ scroll to the fragid if just going back.

Posted from: 216.239.45.4 by ian@hixie.ch


-- 
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 Friday, 5 March 2010 01:30:22 UTC