Closed
Bug 877856
Opened 11 years ago
Closed 8 years ago
Remove obsolete defaultset attributes once Australis lands
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox 50
Tracking | Status | |
---|---|---|
firefox50 | --- | fixed |
People
(Reporter: Gijs, Assigned: aks, Mentored)
References
(Blocks 1 open bug)
Details
(Whiteboard: [lang=js][lang=xul])
Attachments
(1 file)
Per bug 877524 comment #2, we should probably get rid of defaultset attributes which will no longer be used.
Updated•11 years ago
|
Blocks: australis-cust
Updated•11 years ago
|
Whiteboard: [Australis:P5]
Reporter | ||
Comment 1•10 years ago
|
||
Ironically, we now use this for compatibility for addon toolbars. I guess we can remove them from the default toolbars but we can't remove the support for add-ons for some time, I'd expect.
Updated•10 years ago
|
Blocks: fxdesktopbacklog
Whiteboard: [Australis:P5] → [Australis:P5] [feature] p=0
Updated•10 years ago
|
No longer blocks: fxdesktopbacklog
Whiteboard: [Australis:P5] [feature] p=0 → [Australis:P5]
Reporter | ||
Comment 2•9 years ago
|
||
This will need to: - remove all the defaultset attributes from the builtin toolbars (#nav-bar, #TabsToolbar, #toolbar-menubar, #addon-bar, #PersonalToolbar) - add a one-time migrateUI migration that removes all of those attributes from the persist store in case they're in there. - update CustomizableUI's code to never read the attribute for the builtin toolbars
Mentor: gijskruitbosch+bugs
Whiteboard: [Australis:P5] → [lang=js][lang=xul]
Assignee | ||
Comment 3•8 years ago
|
||
Hi Gijs, I am taking this up. I will first tackle the removal of all the defaultset attributes. Where do I need to look at to get started here ?
Assignee: nobody → akshat.kedia
Flags: needinfo?(gijskruitbosch+bugs)
Reporter | ||
Comment 4•8 years ago
|
||
(In reply to Akshat Kedia [:aks] from comment #3) > Hi Gijs, > > I am taking this up. I will first tackle the removal of all the defaultset > attributes. Where do I need to look at to get started here ? In browser.xul, there's a number of <toolbar> elements that have a defaultset attributes. All of those should be removed (and in one case, both 2 versions separated by ifdefs, including the ifdefs themselves, should be removed). (In reply to :Gijs Kruitbosch from comment #2) > - add a one-time migrateUI migration that removes all of those attributes > from the persist store in case they're in there. More precisely, in this method: http://searchfox.org/mozilla-central/rev/3f096f780166bc4772199d79a79c8e3541ff99be/browser/components/nsBrowserGlue.js#1898 - increment the const (at the time of writing it's 38, so it'd become 39), let's say the new value is N - add an if block for (currentUIVersion < N) below the last similar if block there, and inside the if block write code like in this if block: http://searchfox.org/mozilla-central/rev/3f096f780166bc4772199d79a79c8e3541ff99be/browser/components/nsBrowserGlue.js#2067-2074 that removes the 'defaultset' value for all the toolbars (so don't include navigator-toolbox), but include everything else > - update CustomizableUI's code to never read the attribute for the builtin > toolbars I actually think this might not need to happen, and it should work as-is. To make sure this is the case, verify (probably easiest to use logging through Components.utils.reportError) that the code in this if block: http://searchfox.org/mozilla-central/rev/3f096f780166bc4772199d79a79c8e3541ff99be/browser/components/customizableui/CustomizableUI.jsm#620-638 doesn't get executed for the builtin toolbars (ie the ones where you're removing the defaultset attribute browser.xul).
Flags: needinfo?(gijskruitbosch+bugs)
Assignee | ||
Comment 5•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/59080/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/59080/
Attachment #8762280 -
Flags: review?(gijskruitbosch+bugs)
Reporter | ||
Comment 6•8 years ago
|
||
Comment on attachment 8762280 [details] Bug 877856 - Remove obsolete defaultset attributes once Australis lands. Kruitbosch https://reviewboard.mozilla.org/r/59080/#review56130 This looks good, thanks! I assume you verified manually that the builtin toolbars hit the right codepath in the code in comment #4 ?
Attachment #8762280 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 7•8 years ago
|
||
I did Components.utils.reportError(defaultsetAttribute); in here http://searchfox.org/mozilla-central/rev/3f096f780166bc4772199d79a79c8e3541ff99be/browser/components/customizableui/CustomizableUI.jsm#620-638 but the jsconsole did not output anything. I assume that this verifies as expected.
Flags: needinfo?(gijskruitbosch+bugs)
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/fx-team/rev/ea5833a015a1 Remove obsolete defaultset attributes from default toolbars, r=gijs
Reporter | ||
Comment 9•8 years ago
|
||
(In reply to Akshat Kedia [:aks] from comment #7) > I did Components.utils.reportError(defaultsetAttribute); in here > http://searchfox.org/mozilla-central/rev/ > 3f096f780166bc4772199d79a79c8e3541ff99be/browser/components/customizableui/ > CustomizableUI.jsm#620-638 but the jsconsole did not output anything. I > assume that this verifies as expected. Yup, I doublechecked as well, this looks excellent. Landed on fx-team. Thanks!
Flags: needinfo?(gijskruitbosch+bugs)
Assignee | ||
Comment 10•8 years ago
|
||
Great! :)
Comment 11•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ea5833a015a1
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 50
You need to log in
before you can comment on or make changes to this bug.
Description
•