Graduate the panels to the main proton pref
Categories
(Firefox :: Messaging System, task, P3)
Tracking
()
People
(Reporter: mconley, Assigned: emmamalysz)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [proton-door-hangers])
Attachments
(1 obsolete file)
Once bug 1700105, this should be a relatively mechanical find/replace of browser.proton.doorhangers.enabled
to browser.proton.enabled
.
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Once the remaining P1's are closed, is it okay to graduate, or are there other blocking issues before we graduate behind browser.proton.enabled
?
Reporter | ||
Comment 2•4 years ago
|
||
Actually, going to redirect that needinfo to tduzan who's been running point on many panels for Product.
Comment 3•4 years ago
|
||
Just a quick update on this, I am working my way through reviews of the current state of the experience across several platforms. I expect to have a clear answer on this soon. I will ping mconley in Slack with any questions.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
Hey tduzan, since the Proton panels are enabled by default in Nightly, can I presume this bug no longer needs to be P1? "Graduation" at this point is kind of meaningless, at least from an engineering point of view. I suggest downgrading this to a P3.
Updated•4 years ago
|
Comment 6•4 years ago
|
||
I believe that we could graduate this subpref at this point, as well. The issues that previously prevented that have been resolved.
Reporter | ||
Comment 7•4 years ago
|
||
True, this can be done, though I don't think it's critical at this point given that the preference is on by default. I think the P3 priority makes sense.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 9•4 years ago
|
||
Backed out for causing failures at test_chrome_only_media_queries.html:
https://hg.mozilla.org/integration/autoland/rev/bf50f2895a27fc44f5f927d3d1952884270f01ae
Failure log: https://treeherder.mozilla.org/logviewer?job_id=337955422&repo=autoland&lineNumber=4594
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
bugherder |
Comment 12•4 years ago
|
||
There are still several references to browser.proton.doorhangers.enabled:
https://searchfox.org/mozilla-central/search?q=browser.proton.doorhangers.enabled&case=true&path=
Comment 13•4 years ago
|
||
(In reply to Sören Hentzschel from comment #12)
There are still several references to browser.proton.doorhangers.enabled:
https://searchfox.org/mozilla-central/search?q=browser.proton.doorhangers.enabled&case=true&path=
searchfox is just slow to update - compare that list with the patch linked in comment #11
Comment 14•4 years ago
•
|
||
I didn't check all files but at least StaticPrefList.yaml was not touched at all in the patch and you can also check in about:config that browser.proton.doorhangers.enabled still exists (the patch should be included in the tested Nightly build since setting browser.proton.doorhangers.enabled to false no longer adds the arrow to the panels).
Assignee | ||
Comment 15•4 years ago
|
||
All files have removed browser.proton.doorhangers.enabled other than StaticPrefList.yaml. I will create a follow up bug for that and the typo Emilio pointed out in https://phabricator.services.mozilla.com/D110135#3688994
Reporter | ||
Comment 16•4 years ago
|
||
Hey folks,
I've requested the sheriffs to back this out for a few reasons:
- It looks like there's still a bit left to do (see comment 14)
- This is lower priority cleanup work that spans a lot of files which might make crafting upliftable patches more difficult, unless this patch gets uplifted (which it probably shouldn't).
It's even unclear if we need to do this work at this point - the panels have effectively graduated by being enabled. It'll probably just be easier to remove all of the branching when we decide to stop supporting the non-Proton variant.
Comment 17•4 years ago
|
||
Comment 18•4 years ago
|
||
Comment 19•4 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/3ee96c3743a0
Comment 20•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:emalysz, could you have a look please?
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 21•4 years ago
|
||
Given the timeline, plus given bug 1709425 (which aims to remove all of the branching anyways), I think we can WONTFIX this.
Updated•4 years ago
|
Description
•