This is causing https://github.com/mozilla-b2g/gaia/issues/1869#issuecomment-6520055 Exactly why they're calling history.replaceState with no shistory object is...unclear. Calling replaceState is kind of sane, but pushState with no shistory is pretty worrying and probably not what they want. This code is still dead, though. We could leave in the (accidental) assertion that there's a root shistory object for pushState, if you want. Patch once I have it tested...
Created attachment 636309 [details] [diff] [review] Patch v1
Attachment #636309 - Flags: review?(bzbarsky)
Comment on attachment 636309 [details] [diff] [review] Patch v1 r=me
Attachment #636309 - Flags: review?(bzbarsky) → review+
Assignee: nobody → justin.lebar+bug
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.