Add upgrade message on 100 major upgrade with single thank you (3 potential actions)
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox100 | --- | verified |
People
(Reporter: Mardak, Assigned: mviar)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(3 files)
We can build in a message and configure it appropriately. This is different from the previous upgrade spotlights that relied on upgradeDialog code and instead can use the refactored multistage spotlight bug 1739252. Might want fancy title on colorway.
Reporter | ||
Comment 1•3 years ago
|
||
Unpinned users need a pin action. Not default gets a default action. Otherwise a single start browsing button that auto advance.
Reporter | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
My current speculation, without a lot of context looks like this:
We probably want to add the message, using a multistage
template into the OnboardingProvider
, and open the Spotlight dialoig in BrowserGlue.jsm, probably from or around _showUpgradeDialog
.
I haven't self-assigned this bug, because I'm not far enough along that I think it makes sense for me to block anyone on the east coast from grabbing this if they want to in the morning. I'm happy to take it (or whatever is appropriate) Friday, of course. On the off-chance that it's useful, https://gist.github.com/dmose/a6829b5f64980609691bbefcd5e79a3f is the noodling that I've been doing that does not yet open a dialog...
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
bugherder |
Comment 6•3 years ago
|
||
Hi! It looks like this dialog has a few accessibility issues:
- The animated logo is not disabled when a user has prefers-reduced-motion enabled
- The title text becomes invisible for high-contrast black themes, difficult to read on other high contrast dark themes
- Hitting tab initially focuses "not now" instead of the preferred "pin" button
I'll attach screenshots for the invisible text one.
Comment 7•3 years ago
|
||
Comment 8•3 years ago
|
||
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 9•3 years ago
|
||
Thanks Morgan, I've file bug 1763470 to follow up on your findings.
Comment 11•3 years ago
|
||
This enhancement was part of the work done on QA-1448 for which we sent a Preliminary checkpoint. Considering this I am marking it as Verified.
Reporter | ||
Updated•2 years ago
|
Description
•