Closed
Bug 1421642
Opened 7 years ago
Closed 7 years ago
Back button on Facebook closes Facebook instead of undoing the last operation
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox57 unaffected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox57 | --- | unaffected |
People
(Reporter: marco, Unassigned)
Details
(Keywords: regression)
STR:
1) Open facebook.com
2) Go to a Facebook page or profile
3) Press the back button to go back to the Facebook home page
The back button should bring you (and was bringing you) to the previous visited page (in this specific case, the home page). Instead, it closes the Facebook page as if all the actions done on Facebook were not recorded in the history.
Reporter | ||
Comment 1•7 years ago
|
||
Breaking the Facebook website is probably bad, even though I don't know how many people use the Facebook site vs the app.
status-firefox57:
--- → affected
tracking-firefox57:
--- → ?
Reporter | ||
Comment 2•7 years ago
|
||
Note: only reproducible if you open Facebook from a icon on the homescreen.
Comment 3•7 years ago
|
||
The symptoms sound suspiciously similar to bug 1417498, but that one is definitively fixed.
Unfortunately I can't test on release right now and on Nightly I can't reproduce it, but that might be because I'm not logged in to Facebook.
(In reply to Marco Castelluccio [:marco] from comment #0)
> 2) Go to a Facebook page or profile
If you check the back button at this point, it's still showing greyed out, right? Also, did the URL bar update, or does it keep on showing facebook.com, even though normally it should have changed by this point to whatever page you're viewing now?
Can you
1. Test opening facebook.com from the context menu in a new tab (either through a link or from one of the home panels), so it'll be the first session history entry for that tab instead of the usual entry for about:home you get when opening a new empty tab and then manually navigating to facebook.com?
2 Turn on "consoleservice.logcat" in about:config (might need a browser restart to take effect, not sure) and get a logcat log of this happening?
Flags: needinfo?(mcastelluccio)
Comment 4•7 years ago
|
||
(In reply to Jan Henning [:JanH] from comment #3)
> The symptoms sound suspiciously similar to bug 1417498, but that one is
> definitively fixed.
... and only ever affected 58 and 59.
Reporter | ||
Comment 5•7 years ago
|
||
I can't reproduce the bug anymore. Maybe it was an issue on the Facebook side?
I will reopen if I can reproduce again.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mcastelluccio)
Resolution: --- → WORKSFORME
tracking-firefox57:
? → ---
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•