Closed
Bug 1485438
Opened 6 years ago
Closed 6 years ago
new @search feature and new tab page broken
Categories
(Firefox :: New Tab Page, defect, P2)
Firefox
New Tab Page
Tracking
()
RESOLVED
WORKSFORME
Iteration:
64.3 - Oct 12
People
(Reporter: aryx, Unassigned)
References
Details
Attachments
(1 file)
8.19 KB,
text/x-log
|
Details |
Firefox 62.0b19 candidate 1 (repackaged from English (US) to German) on Windows 8.1 After Firefox had been repackaged and got launched in a testing profile (without extensions), I typed something in the search field of the home page, pressed Esc to hide the search suggestions and then clicked on a search tile (Amazon, if I remember correct) and nothing happened. Opening new tabs showed just a a gray area as content. Firefox Options/Preferences > Home missed the whole "Firefox Home Content" section. Closing and launching Firefox again didn't reproduce the issue. From the browser console: [Mitteilungsdetails anzeigen/ausblenden] TypeError: extension is undefined receiveMessage@resource://gre/modules/ExtensionParent.jsm:349:1 _handleMessage/</<@resource://gre/modules/MessageChannel.jsm:912:19 _handleMessage/<@resource://gre/modules/MessageChannel.jsm:911:9 _handleMessage@resource://gre/modules/MessageChannel.jsm:909:7 receiveMessage/<@resource://gre/modules/MessageChannel.jsm:208:9 receiveMessage@resource://gre/modules/MessageChannel.jsm:201:5 MessageChannel.jsm:914 TypeError: addon is null[Weitere Informationen] XPIProvider.jsm:2579:36
Comment 1•6 years ago
|
||
The log does have the deprecation warning bug 1482579, and that the search tile was shown initially means the content and services were running.. [Mitteilungsdetails anzeigen/ausblenden] DEPRECATION WARNING: Search service falling back to synchronous initialization. This is generally the consequence of an add-on using a deprecated search service API. You may find more details about this deprecation at: https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIBrowserSearchService#async_warning jar:file:///F:/Ablage/Temp/Trash/firefox/omni.ja!/components/nsSearchService.js 2675 SRCH_SVC__ensureInitialized jar:file:///F:/Ablage/Temp/Trash/firefox/omni.ja!/components/nsSearchService.js 4086 get currentEngine resource://activity-stream/lib/TopSitesFeed.jsm 55 getShortURLForCurrentSearch resource://activity-stream/lib/TopSitesFeed.jsm 79 init resource://activity-stream/lib/TopSitesFeed.jsm 638 onAction resource://activity-stream/lib/Store.jsm 51 _middleware/</< resource://activity-stream/lib/Store.jsm 29 Store/this[method] resource://activity-stream/lib/Store.jsm 140 init Deprecated.jsm:77 Although clicking on the search tile not filling in the address bar seems to indicate messages weren't getting from content to main? The missing preferences also seems to indicate something on main failed to finish loading.
See Also: → 1482579
Comment 2•6 years ago
|
||
Mmm.. I wonder if this has anything to do with the file located in trash? jar:file:///F:/Ablage/Temp/Trash/firefox/omni.ja!/…
Reporter | ||
Comment 3•6 years ago
|
||
The folder is just named trash, means anything I am willing to throw away. But it hasn't any special bits sets. Maybe at least some of this is not directly related to AS but system addons? PDF handling also seems to be broken (always downloads them).
Reporter | ||
Comment 4•6 years ago
|
||
Forget about the PDF stuff, also happens with builds directly from Mozilla.
Comment 5•6 years ago
|
||
There do seem to be a bunch of extension related failures in the log. Odd that the content page loaded enough to display the pinned search tile but didn't finish to be able to handle messages or preferences… ? (A prerendered page would show wireframes -- e.g., resource://activity-stream/prerendered/de/activity-stream-prerendered.html assuming default prefs -- but for urls and images to have loaded, it must have received a message from main.)
Updated•6 years ago
|
Iteration: --- → 64.1 (Sep 14)
Priority: -- → P2
Updated•6 years ago
|
tracking-firefox63:
--- → ?
Comment 6•6 years ago
|
||
Tim, you requested tracking for 63, is your team working on a fix we should follow for 63? Thanks
Flags: needinfo?(tspurway)
Comment 7•6 years ago
|
||
hey Pascal, we are working on this bug this iteration, and hope to have a fix by 9/14
Flags: needinfo?(tspurway)
Updated•6 years ago
|
Updated•6 years ago
|
Iteration: 64.1 (Sep 14) → 64.2 (Sep 28)
Updated•6 years ago
|
status-firefox62:
--- → affected
Updated•6 years ago
|
status-firefox63:
--- → affected
Updated•6 years ago
|
status-firefox64:
--- → affected
Updated•6 years ago
|
Iteration: 64.2 (Sep 28) → 64.3 (Oct 12)
Updated•6 years ago
|
Assignee | ||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
You need to log in
before you can comment on or make changes to this bug.
Description
•