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, Unassigned)
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•5 years ago
|
||
Peter, can you help shed some light? Thank you.
|
Reporter | |
Comment 3•5 years ago
|
||
Assuming https://bugzilla.mozilla.org/show_bug.cgi?id=1515073 is related here?
|
||
Comment 4•5 years ago
|
||
This is being worked on in Bug 1644595.
|
||
Comment 5•5 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.
|
|
||
Comment 6•5 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.
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
||
Comment 7•4 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•4 years ago
|
||
This is also affecting sammobile.com, as seen in https://github.com/webcompat/web-bugs/issues/72838
|
|
||
Comment 9•4 years ago
|
||
|
||
Updated•3 years ago
|
|
||
Comment 13•1 year ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
|
|
||
Comment 14•10 months ago
|
||
(In reply to Emily Kager [:ekager] from comment #0)
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 confirmed that I cannot reproduce the issue on indiatoday.in with Nightly Fx 132, while I can still reproduce the problem with older versions, Fx 94 and Fx 102.
(In reply to Thomas Wisniewski [:twisniewski] from comment #9)
I still see the issues with this site. I also see the same issues on Chrome.
Adam, is this another symptom of the "redirect" case?
|
||
Comment 15•10 months ago
|
||
(In reply to Hsin-Yi Tsai (she/her) [:hsinyi] from comment #14)
(In reply to Emily Kager [:ekager] from comment #0)
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 confirmed that I cannot reproduce the issue on indiatoday.in with Nightly Fx 132, while I can still reproduce the problem with older versions, Fx 94 and Fx 102.
(In reply to Thomas Wisniewski [:twisniewski] from comment #9)
I still see the issues with this site. I also see the same issues on Chrome.
Adam, is this another symptom of the "redirect" case?
Yeah, the page seems to be triggering pushState whenever a scroll occurs - which seems to happen every time it loads a photo, generating a ton of history entries whenever you navigate to the page. Blink and Webkit both behave the same way we do here.
|
|
||
Comment 16•8 months ago
|
||
I am closing this bug.
The original report on https://www.indiatoday.in/india/story/air-india-passenger-tests-coronavirus-positive-1682333-2020-05-27 is fixed.
The other report on https://www.aajtak.in/entertainment/television/photo/krushna-abhishek-birthday-love-story-with-kashmira-shah-affair-govinda-tmov-1263266-2021-05-30-3 is invalid for us, as comment 15 explained. Chrome behaves the same here - it's a website's behavior.
|
||
Comment 17•8 months ago
•
|
||
Verified using latest Nightly Firefox 135.0a1 on Windows 10, macOS 12 and Ubuntu 22, works as expected if not using affected websites like aajtak.in, sammobile.com.
|
||
Comment 18•8 months ago
|
||
Verified as fixed also on Android on the latest Nightly Firefox 135.0a1 with Samsung Galaxy S23 Ultra (Android 14).
|
|
||
Updated•8 months ago
|
Description
•