Need to press back many times on indiatoday.in to go back in history
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
Webcompat Priority | P3 |
People
(Reporter: ekager, Assigned: johannh)
References
(Blocks 2 open bugs)
Details
I can reproduce on Fenix Beta, Nightly, and Fennec so it definitely belongs in another component, but I'm not sure where to put it.
Originally reported: https://github.com/mozilla-mobile/fenix/issues/8180#issuecomment-635058925
STR:
-
Scroll to the bottom of the page, and to the top again. And stay there for a few seconds (3 to 4 seconds would be enough)
-
Press the back button, observe that it take more than a single press to go back and sometimes it just refuses to go back and sometimes it takes several clicks before it works.
I think this is related to abuse (or at least misuse) of the History API. There are 5 entries in window.history
after doing the STR above.
Hsin-Yi, do you know if there is any effort underway to prevent this type of thing? I'll keep this bug for mitigating these types of things and post a workaround on the Fenix bug.
Comment 2•4 years ago
|
||
Peter, can you help shed some light? Thank you.
Reporter | ||
Comment 3•4 years ago
|
||
Assuming https://bugzilla.mozilla.org/show_bug.cgi?id=1515073 is related here?
Comment 4•4 years ago
|
||
This is being worked on in Bug 1644595.
Assignee | ||
Comment 5•4 years ago
|
||
Hmm, this is improved upon by bug 1515073, but it doesn't feel fixed as in the page will very aggressively add history entries while you interact with it, breaking our heuristic. Chrome seems unaffected, so it's probably worth checking what they do differently there.
Assignee | ||
Comment 6•4 years ago
|
||
I suspect that this is because unlike Chrome we're marking SH entries from cross-origin iframe navigations even if only the parent document received user interaction. We need to ensure that when we get user interaction we only mark it if the document that received the interaction is same-origin with that SH entry.
Or something like that.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 7•3 years ago
|
||
This is still an issue. It was reported on Firefox for Android even for popular sites like bing: https://github.com/mozilla-mobile/fenix/issues/17987#issuecomment-814853381.
Comment 8•3 years ago
|
||
This is also affecting sammobile.com, as seen in https://github.com/webcompat/web-bugs/issues/72838
Comment 9•3 years ago
|
||
Updated•3 years ago
|
Description
•