Add a delay between the default Set to Default prompt and showing the INFOBAR_DEFAULT_AND_PIN_87 message
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: mviar, Assigned: hanna_a)
References
Details
Attachments
(1 file)
The INFOBAR_DEFAULT_AND_PIN_87 message's targeting may be perceived as not respecting the browser.shell.checkDefaultBrowser pref (this can be set using a checkbox in about:settings). Its targeting includes !isDefaultBrowser && !'browser.shell.checkDefaultBrowser'|preferenceValue.
David Rubino raised this issue on Slack.
| Reporter | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
INFOBAR_DEFAULT_AND_PIN_87 showing on targeting !isDefaultBrowser && !'browser.shell.checkDefaultBrowser'|preferenceValue is working as expected. see discussion in implementing https://bugzilla.mozilla.org/show_bug.cgi?id=1703874#c0
This infobar shows as an edgecase only for users who dismissed the set default modal prompt by clicking on checkbox (setting pref browser.shell.checkDefaultBrowser to false) and are profile age between 5 and 15 weeks.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 2•1 year ago
|
||
Product suggestion from Alex Davis on Slack - allow the infobar message, waiting some amount a time after the last time they saw the original set to default pop-up.
| Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
NI @Vtay How long should we delay showing the infobar after user last checked 'don't show me set default prompt message again' ? Would 24 hours be enough?
Updated•1 year ago
|
Comment 5•1 year ago
•
|
||
NI @hanna to clarify if this fix is an uplift candidate Thanks!
| Assignee | ||
Comment 6•1 year ago
|
||
Hi @punam, The infobar is shown to a limited amount of users due to it's targeting conditions, and this bug is not a defect but more of a enhancement so I don't think it needs to be uplifted. I'll update it to 138.
Comment 9•1 year ago
|
||
There's a message on remote settings with the same id and it still has the old configuration. Is it overriding this? It comes first in the array, which should mean it's returned first by triggers, which should mean the changes here have no effect.
Try it in console: ChromeUtils.importESModule("resource:///modules/asrouter/ASRouter.sys.mjs").ASRouter.state.messages.filter(m => m.id === "INFOBAR_DEFAULT_AND_PIN_87")
I think we ought to remove the remote settings message. Clearly having it tucked away in a location that is now so obscure is creating pitfalls for us to step in.
Description
•