If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

history.forward() does not trigger hashchange

NEW
Unassigned

Status

()

Core
DOM
P2
normal
a month ago
a month ago

People

(Reporter: Domenic Denicola, Unassigned)

Tracking

55 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

a month ago
Test: http://w3c-test.org/html/browsers/browsing-the-web/scroll-to-fragid/forward-triggers-hashchange.html

Edge and Chrome both pass. (Haven't tested Safari)
Thanks. Gijs and smaug, I feel like we've discussed this before but maybe that wasn't in the context of the History API.
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(bugs)
Priority: -- → P2

Comment 2

a month ago
(In reply to Andrew Overholt [:overholt] from comment #1)
> Thanks. Gijs and smaug, I feel like we've discussed this before but maybe
> that wasn't in the context of the History API.

I'm afraid I don't really recall... were you thinking of someone else? :-)

Assuming this also happens for history.back(), this looks like a dupe of bug 1052783. (Though maybe we want to keep them separate to track wpt things? I don't know.)

I won't have cycles to work on this before photon ships (and am probably not the right person anyway).
Flags: needinfo?(gijskruitbosch+bugs)
(In reply to :Gijs from comment #2)
> (In reply to Andrew Overholt [:overholt] from comment #1)
> > Thanks. Gijs and smaug, I feel like we've discussed this before but maybe
> > that wasn't in the context of the History API.
> 
> I'm afraid I don't really recall... were you thinking of someone else? :-)

I think it was more general navigation things around the location bar and docshell and hashchanges. But Anne and I spoke about this earlier today and it's clear to me now that it's just a bigger set of issues.

> Assuming this also happens for history.back(), this looks like a dupe of bug
> 1052783. (Though maybe we want to keep them separate to track wpt things? I
> don't know.)

Let's keep them separate for now. Thanks for the reference to that bug!
Flags: needinfo?(bugs)
(Reporter)

Comment 4

a month ago
FWIW, I saw https://bugzilla.mozilla.org/show_bug.cgi?id=1052783 but thought that since document.write() was involved, it was potentially a different pathology. This test case doesn't involve document.write() but still triggers a similar issue.

(Might still be the same root cause, of course.)
You need to log in before you can comment on or make changes to this bug.