Closed Bug 1685089 Opened 3 years ago Closed 3 years ago

Ship resetting


(Core :: DOM: Core & HTML, task)




86 Branch
Tracking Status
firefox86 --- fixed


(Reporter: annevk, Assigned: timhuang)


(Blocks 1 open bug)


(Keywords: dev-doc-complete)


(1 file)

  1. Announce intent to ship on dev.platform.
  2. Flip
  3. File follow-up bug for removal of once it's been flipped for a couple of releases.

About 1,

We have sent out the intent to ship before. See

While I was doing some Fission work I realized that there seems to be an issue in the name resetting implementation even without Fission.
Filing a bug with a testcase in a moment.

Severity: -- → S3
Depends on: 1687390
Depends on: 1687527
Pushed by
Enable resetting. r=dimi

Exciting, great work Tim!

Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch

Rumyra has documented this one; see for details. Basically it was already documented; we just needed to update the compat data and provide a rel note to make it clear that this is now shipped.

Let us know if you think this needs anything else. Thanks!

I want to bring to attention that this change broke protractor (automated testing tool) with angular.js. See for details.
Short story: is used as a signaling "channel" for the external testing code, to indicate the page JS has initialised.

Maybe it could be nice to keep the pref around, or make FirefoxDriver not reset at all?

Chris, thanks for highlighting that. Could you file a new bug against FirefoxDriver/DevTools so we can consider that and your suggestion does not get lost? (And maybe link it from here afterwards in case others are curious.)

Regressions: 1700931

Anne, thanks for the suggestion. I've filed #1700931 but cannot find the proper component for FirefoxDriver. Maybe you could fix that bugs metadata? Thanks!

thank you for your work on limiting leaks, however, the current implementation leaves wide open all leaks that occur after is used, even if the call to does not specify a window name, for example ...

  1. calls'')
  2. specifies'blahblah'
  3. user enters '' in the location bar
  4. calls alert(, which will show 'blahblah' that was set by
Flags: needinfo?(tihuang)

That's correct and out-of-scope of this bug. We track that general class of problems in bug 1657250.

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