Closed
Bug 1488914
Opened 6 years ago
Closed 6 years ago
tabs.create and windows.create should open about:privatebrowsing instead of about:newtab in PB
Categories
(WebExtensions :: Frontend, enhancement, P1)
WebExtensions
Frontend
Tracking
(firefox64 verified, firefox65 verified)
People
(Reporter: robwu, Assigned: robwu)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
While testing bug 1393570 I found that new windows and new tabs default to about:newtab even in private browsing mode. When the window is in private browsing mode, the default should be about:privatebrowsing. This expected behavior is the case when a new private tab/window is opened manually by the user.
Comment 1•6 years ago
|
||
That's strange, because I notice new windows opening with about:privatebrowsing in tests I've done for bug 1345474.
Comment 2•6 years ago
|
||
on second thought, I might not using webext apis to open windows.
Updated•6 years ago
|
Priority: -- → P1
Assignee | ||
Comment 3•6 years ago
|
||
This is actually a regression, and should be fixed before Beta is promoted to stable. ...and windows.create for non-private browsing windows should be about:home (but that is not a regression). https://phabricator.services.mozilla.com/D4929#inline-20894
Blocks: 1362034
status-firefox62:
--- → unaffected
status-firefox63:
--- → affected
status-firefox64:
--- → affected
Keywords: regression
See Also: → 1485307
Assignee | ||
Comment 4•6 years ago
|
||
I'm mistaken, this is not a regression. Unlike windows.create, tabs.create does not use newTabService. The default hoempage of windows.create is still broken though, both for private and non-private windows.
status-firefox62:
unaffected → ---
status-firefox63:
affected → ---
status-firefox64:
affected → ---
Keywords: regression
See Also: 1485307 →
Assignee | ||
Comment 5•6 years ago
|
||
Use a homepage URL instead of a new tab URL by default in browser.windows.create.
Assignee | ||
Updated•6 years ago
|
Iteration: --- → 64.2 (Sep 28)
Comment hidden (obsolete) |
Updated•6 years ago
|
Attachment #9015851 -
Attachment is obsolete: true
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/c844033d55eb Use about:home / about:privatebrowsing in windows.create r=rpl,dao
Comment 8•6 years ago
|
||
Backed out changeset c844033d55eb (Bug 1488914) for bc failures in /browser_ext_windows_create_cookieStoreId.js. Backout: https://hg.mozilla.org/integration/autoland/rev/04fbac02c101394f6b344a695e81bdfb026151a1 Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending,running,success,testfailed,busted,exception&revision=c844033d55eb91acb4190ee202361b1b95062e0c&selectedJob=204838242 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=204838242&repo=autoland&lineNumber=3660
Flags: needinfo?(rob)
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(rob)
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/cf62153b17ad Use about:home / about:privatebrowsing in windows.create r=rpl,dao
Comment 10•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cf62153b17ad
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Comment 11•6 years ago
|
||
Verified that the issue is no longer occurring on: FF 64.0b3, Nightly 65.0a1 running on Windows 10 x64, using both browser's controls and tab management extensions.
You need to log in
before you can comment on or make changes to this bug.
Description
•