The tab note on Instagram is retained after navigating from a post to the home page using Back browser button
Categories
(Firefox :: Tabbed Browser, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | verified |
People
(Reporter: rpopovici, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fidefe-tabgrps])
Note
- The tab note on Instagram is retained after navigating from a post to the home page using the Back browser button. The tab note disappears after the page is refreshed.
Found in
- Nightly v149.0a1
Affected versions
- Nightly v148.0a1
- Nightly v149.0a1
Tested platforms
- Affected platforms: all
- Unaffected platforms: none
Steps to reproduce
- Load https://www.instagram.com/ and log in.
- Click on a post.
- Add a note.
- Click the browser's "back" button to return to the home page.
- Observe the tab note.
Expected result
- The Instagram home page is reloaded; the tab note should not be displayed on the home page.
Actual result
- The Instagram home page is reloaded.
- The tab note is retained. The tab note disappears after the page is refreshed.
Regression range
- Not a regression.
| Reporter | ||
Updated•6 months ago
|
| Reporter | ||
Updated•6 months ago
|
Comment 1•6 months ago
|
||
Another STR of essentially the same problem:
- Log into Instagram.
- Reach a profile
- Click on a post to bring into view. (URL changes)
- Attach a note
- Click on "X" or outside of the post area to refocus the profile. (URL changes back)
Expected: Note icon disappears.
Actual: Note icon remains displayed. Refresh fixes the issue.
The same issue occurs the other way around: If a note should be displayed, it won't before refreshing the page.
Updated•6 months ago
|
Updated•6 months ago
|
Comment 2•6 months ago
|
||
Doesn't seem like Instagram is using canonical links in their pages, so we are always using the full URL.
They are using history.pushState and when we use the back button, it seems like we're not receiving the pageshow event like we're expecting.
Comment 3•6 months ago
|
||
This issue no longer occurs in the latest Nightly v149.0a1 from 2026-02-06, but random failure occurances are still observed; Clear steps to reproduce could not be determined. An issue related to timing is suspected.
This report can be closed as fixed. Any possible follow-up issues will be reported during the next testing phase. Thank you!
sthompson: Can you close this report as fixed? Thanks.
Updated•5 months ago
|
Description
•