Page MenuHomePhabricator

Possible fix for JX.History spookiness?
ClosedPublic

Authored by epriestley on Apr 20 2015, 11:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jun 28 2025, 2:50 PM
Unknown Object (File)
Jun 27 2025, 10:22 PM
Unknown Object (File)
Jun 27 2025, 9:13 PM
Unknown Object (File)
Jun 6 2025, 2:48 PM
Unknown Object (File)
Apr 30 2025, 1:55 AM
Unknown Object (File)
Apr 30 2025, 1:54 AM
Unknown Object (File)
Apr 19 2025, 1:07 PM
Unknown Object (File)
Apr 18 2025, 7:54 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
T7573: Ship Quicksand
Commits
Restricted Diffusion Commit
rP1602858b2662: Possible fix for JX.History spookiness?
Summary

Ref T7573. I only got this reproducing like 10% of the time in Firefox but I can't reproduce it anymore after this change.

Test Plan
  • Added some logging.
  • Saw Firefox handing us nonsense state values (?)
  • Read the Firefox documentation?
  • Maybe state is expected to be an object? This shouldn't matter?
  • I don't really know?

iiam

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Possible fix for JX.History spookiness?.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
This revision is now accepted and ready to land.Apr 20 2015, 11:35 PM
This revision was automatically updated to reflect the committed changes.

This didn't fix it for me unfortunately...

  • load /p/btrahan
    • observe debug output of path that's getting put into _history member variable: /p/btrahan/
  • click /p/btrahan/feed/ link
    • Quicksand.js:270 Object {path: "/p/btrahan/feed/", state: 1}
  • click back
    • Quicksand.js:270 Object {path: "/p/btrahan/", state: 2}
    • this should be 0...?

Yeah, it should be 0. I don't even know where the 2 is coming from. Locally when I repro'd this, we never pushed 2 into the state in the same window that I could see.