Closed Bug 1554238 Opened 1 year ago Closed 1 year ago

Remove `richlistitem` and `category` bindings

Categories

(Toolkit :: XUL Widgets, task, P5)

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: surkov, Assigned: ntim)

References

(Depends on 1 open bug)

Details

Attachments

(1 file)

when all UI stuff of about:addons are done (bug 1505924), then remove richlistbox.xml and extensions.xml bindings which are no longer in use:

No longer blocks: 1505924
Depends on: 1505924
Summary: remove richlistbox and extesnions bindings → remove richlistbox and extensions bindings
Priority: -- → P5
Depends on: 1558982
No longer depends on: 1505924
Assignee: nobody → ntim.bugs
Status: NEW → ASSIGNED
Summary: remove richlistbox and extensions bindings → Remove `richlistitem` and `category` bindings

Well, the minimal changes I've planned unfortunately require string ID changes.
This will also be the case when rewriting this to HTML, so I guess I'll let that happen instead to avoid having to change the string ID twice :/

Anyway, if anyone wants to finish this off, the patch is attached.

Assignee: ntim.bugs → nobody
Status: ASSIGNED → NEW

Mark, is there any compelling reason to actually convert the category list to HTML? richlistbox is a xul custom element, so with this patch about:addons will be xbl free and won't be blocking any immediate de-xul work. Should we just finish this patch as-is and move on?

Flags: needinfo?(mstriemer)
Attachment #9078575 - Attachment description: Bug 1554238 - Remove 'richlistitem' and 'category' bindings. (WIP) → Bug 1554238 - Remove 'richlistitem' and 'category' bindings.

I don't think it needs to be converted to HTML here.

Flags: needinfo?(mstriemer)
Pushed by ntim.bugs@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/c6d99b3e8e87
Remove 'richlistitem' and 'category' bindings. r=aswan
Assignee: nobody → ntim.bugs
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.