Remove the "listheader" binding and move the remaining styles to "richlistbox.css"

RESOLVED FIXED in Firefox 63

Status

()

P1
normal
RESOLVED FIXED
9 months ago
8 months ago

People

(Reporter: Paolo, Assigned: Paolo)

Tracking

(Blocks: 1 bug)

Trunk
mozilla63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

9 months ago
The "listheader" binding was originally used in "listbox" is a way that was similar to "treecol", but it was then used in "richlistbox" in a way that was more similar to "treecols".

Since this element is not used anymore in the "treecol" way and its content is always overridden, the binding can be removed and the styles that control color can be moved to "richlistbox.css" in preparation for the removal of the "listbox" element.
Comment hidden (mozreview-request)
(Assignee)

Updated

9 months ago
Blocks: 1472556
(Assignee)

Updated

9 months ago
Blocks: 1472555
(Assignee)

Updated

9 months ago
Blocks: 1474108
(Assignee)

Updated

9 months ago
No longer blocks: 1474108
Depends on: 1474108
Comment hidden (mozreview-request)

Comment 3

9 months ago
mozreview-review
Comment on attachment 8990682 [details]
Bug 1474258 - Remove the "listheader" binding and move the remaining styles to "richlistbox.css".

https://reviewboard.mozilla.org/r/255764/#review262576

r=me - assuming Comment 0 is correct in that there are no longer any comsumers of the listheader within a listbox
Attachment #8990682 - Flags: review?(bgrinstead) → review+

Comment 4

9 months ago
Pushed by paolo.mozmail@amadzone.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/bd281782dc93
Remove the "listheader" binding and move the remaining styles to "richlistbox.css". r=bgrins

Comment 5

9 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/bd281782dc93
Status: ASSIGNED → RESOLVED
Last Resolved: 9 months ago
status-firefox63: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
(Assignee)

Updated

8 months ago
See Also: bug 1475202
You need to log in before you can comment on or make changes to this bug.