Open Bug 2009426 Opened 7 months ago Updated 5 months ago

The tab note on X.com/home disappear when using Back/Forward browser navigation buttons

Categories

(Firefox :: Tabbed Browser, defect)

Firefox 148
Desktop
All
defect

Tracking

()

Tracking Status
firefox148 --- affected
firefox149 --- affected

People

(Reporter: rpopovici, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [fidefe-tabgrps])

Attachments

(1 file)

Attached video xhomepage.mp4

Note

  • A tab note on X.com/home is not retained when using the browser's Back/Forward navigation buttons.

Found in

  • Nightly v148.0a1

Affected versions

  • Nightly v148.0a1

Tested platforms

  • Affected platforms: all
  • Unaffected platforms: none

Steps to reproduce

  1. Load https://x.com/home
  2. Add a note.
  3. Click on a thread to open it
  4. Click the browser's "back" button.

Expected result

Actual result

  • The https://x.com/home is reloaded.
  • The note is not displayed. After refreshing the page, the note reappears. Please see the screen recording.

Regression range

  • Not a regression.
Has STR: --- → yes
QA Whiteboard: [S3][qa-found-in-c148]
QA Whiteboard: [S3][qa-found-in-c148] → [QA-4574][qa-found-in-c148][S3]
Blocks: tab-notes
Whiteboard: [fidefe-tabgrps]

We're hitting this case https://searchfox.org/firefox-main/rev/131497bb1b747587b2b21b1abf14f44ecffad805/browser/components/tabnotes/TabNotesController.sys.mjs#208-221 where hitting the back button is treated as same-page history navigation, but CanonicalURLChild is not receiving pageshow. This seems to be happening between any two pages on x.com, not just the main page.

See Also: → 2011721

This issue still occurs in Nightly v149.0a1 from 2026-02-05 (with the fix in bug 2011721 or any later ones).
It was tested in Windows 10, MacOS 14 M1 and Ubuntu 24. This report remains valid and opened.

I've set the info request to make sure you are aware of this information.

Flags: needinfo?(sthompson)
Blocks: 2015071
No longer blocks: 2015071
Duplicate of this bug: 2012053

Looks like Twitter is leaving the <link rel="canonical"> from the previous page in the DOM when going back, so it seems like back/forward is not going to work well for Twitter unless we write site-specific compatibility for it.

Flags: needinfo?(sthompson)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: