Closed
Bug 1605280
Opened 4 years ago
Closed 4 years ago
Newtab search handoff fails when browser.tabs.remote.separatePrivelegedContentProcess is true
Categories
(Firefox :: New Tab Page, defect)
Firefox
New Tab Page
Tracking
()
VERIFIED
FIXED
Firefox 73
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox71 | --- | unaffected |
| firefox72 | --- | unaffected |
| firefox73 | --- | verified |
People
(Reporter: squib, Assigned: squib)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
This is happening because handoff-based search is handled in a new script file, contentSearchHandoffUI.js, and I forgot to add a reference to it in the appropriate spot in AboutNewTabService.jsm.
|
Assignee | |
Comment 1•4 years ago
|
||
Pushed by jporter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ba479d2d0a17 Newtab search handoff fails when browser.tabs.remote.separatePrivelegedContentProcess is true; r=Mardak
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
|
||
Updated•4 years ago
|
Keywords: regression
|
||
Updated•4 years ago
|
status-firefox71:
--- → unaffected
status-firefox72:
--- → unaffected
status-firefox-esr68:
--- → unaffected
|
||
Comment 4•4 years ago
|
||
I have verified that this issue is no longer reproducible with the latest Firefox Nightly (73.0a1 Build ID - 20200106092427) installed, on Windows 10 x64, Ubuntu 18.04 x64 and Mac 10.15.2. Now, the in-content search bar is correctly displayed on the "about:newtab" page if the "browser.tabs.remote.separatePrivilegedContentProcess" pref is set to "true".
Status: RESOLVED → VERIFIED
|
||
Updated•4 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•