Wait for builtin-newtab.js to signal that it has finished onStartup before allowing ActivityStream to be instantiated
Categories
(Firefox :: New Tab Page, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox139 | --- | unaffected |
firefox140 | + | fixed |
firefox141 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 1 open bug)
Details
(Whiteboard: [hnt-trainhop])
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
We have a routine here that attempts to wait for the built-in newtab addon to be ready (and to have run its onStartup routine in builtin-newtab.js) before proceeding with instantiating and initializing ActivityStream.
According to willdurand, despite waiting for the readyPromise on the addon, there are still potentially cases where the builtin-newtab.js's onStartup routine will still not have run. Looking at some Telemetry, it looks like despite no clients firing false
for the addonReadySuccess
metric here, we are seeing clients sending false
for activityStreamCtorSuccess
here.
I think if we can have the AboutNewTabRedirector hold on to a Promise instance, and have that Promise resolve when the builtin-newtab.js finishes running onStartup, we can have AboutNewTab.sys.mjs's onBrowserReady wait for that.
I'll move the addonReadySuccess
metric into builtin-newtab.js to also help us determine if something in there happens to throw for some reason.
Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Comment 2•2 months ago
|
||
[Tracking Requested - why for this release]:
I'll also want to get this uplifted to 140 Beta for our newtab train-hop test later in June.
Updated•2 months ago
|
Updated•2 months ago
|
Comment 4•2 months ago
|
||
bugherder |
Assignee | ||
Comment 5•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D251397
Updated•2 months ago
|
Comment 6•2 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Some users may experience a race condition where their newtab / home pages are blank for the remainder of their browsing session.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: N/A
- Risk associated with taking this patch: Low.
- Explanation of risk level: Instead of waiting for the AddonManager to say that the addon has finished running through startup, we're having the addon tell AboutNewTab instead. It's just a minor shuffling of responsibility.
- String changes made/needed: None.
- Is Android affected?: no
Updated•2 months ago
|
Updated•2 months ago
|
Description
•