disabling e10s would lead to window.name returns "tabbrowser-initialBrowser"

RESOLVED WORKSFORME

Status

()

defect
P5
normal
RESOLVED WORKSFORME
11 months ago
11 months ago

People

(Reporter: yuchang.guo, Unassigned)

Tracking

60 Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180621121604

Steps to reproduce:

1.open about:config
2. change below items (if have) to false
  browser.tabs.remote.autostart
  browser.tabs.remote.autostart.2
3. close Firefox and restart Firefox.
4. navigate to below simple page

File Name: test_firefox60_load_simple.htm
File Content:
<html>
<body>
<script>
document.write("("+window.name+")");
</script>
</body>
</html>


Actual results:

You will see the page output:
 (tabbrowser-initialBrowser) 


Expected results:

The page should output:
()
the reproducible version is 60.1.0esr (32-bit)
It might relate to Bug 1442651 Remove the tabbrowser element and binding
Flags: needinfo?(dao+bmo)
> 2. change below items (if have) to false
>   browser.tabs.remote.autostart
>   browser.tabs.remote.autostart.2

Do we need to keep supporting these prefs?
Component: Untriaged → Tabbed Browser
Flags: needinfo?(dao+bmo) → needinfo?(mconley)
Priority: -- → P5
Depends on: 1486079
We need to continue supporting the notion of non-remote browsers (for things like about:preferences, about:config, etc), but disabling e10s is no longer a supported configuration, no.
Flags: needinfo?(mconley)
Hi Mike,Dão,

We suggest, at least, there is way to disable e10s (multiprocess).
This bug is P5 bug, which is a low priority.
Bug 1486079 removed the tabbrowser-initialBrowser id so I'm guessing it fixed this.
Status: UNCONFIRMED → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.