Closed
Bug 1588515
Opened 6 years ago
Closed 6 years ago
TypeError: document.getElementById(...) is null in permanent private browsing mode
Categories
(Firefox :: General, defect, P3)
Tracking
()
People
(Reporter: mcs, Assigned: mak)
Details
(Whiteboard: [tor 31955])
Attachments
(2 files)
|
1.21 KB,
patch
|
Details | Diff | Splinter Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review |
There is some code inside nonBrowserWindowStartup() that assumes it is operating inside the hidden window. This causes JS errors when permanent private browsing mode is enabled on macOS; for example, when windows such as Page Info are opened. STR:
- Enable permanent private browsing mode via "Never remember history" in about:preferences or by toggling
browser.privatebrowsing.autostartto true. - Restart Firefox.
- Load any page, e.g., https://www.mozilla.org/en-US/
- Press Cmd+I
Check the Browser Console for a message like the following:
TypeError: document.getElementById(...) is null nonbrowser-mac.js:107:14
nonBrowserWindowStartup chrome://browser/content/nonbrowser-mac.js:107
We patched this in Tor Browser; see https://trac.torproject.org/projects/tor/ticket/31955
I will attach the patch.
| Assignee | ||
Comment 1•6 years ago
|
||
Could you please convert the patch to a phabricator review request?
Flags: needinfo?(mcs)
| Assignee | ||
Comment 2•6 years ago
|
||
I'll take it.
Assignee: nobody → mak
Status: NEW → ASSIGNED
Flags: needinfo?(mcs)
| Assignee | ||
Updated•6 years ago
|
Priority: -- → P3
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Iteration: --- → 72.1 - Oct 21 - Nov 3
Points: --- → 1
Pushed by mak77@bonardo.net:
https://hg.mozilla.org/integration/autoland/rev/f775758e2976
TypeError: document.getElementById(...) is null in permanent private browsing mode on Mac. r=Gijs
Comment 5•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•