Closed Bug 1474193 Opened Last year Closed Last year

loading richlistbox.css as a document stylesheet causes design regression in add-ons manager

Categories

(Toolkit :: Themes, defect)

defect
Not set

Tracking

()

VERIFIED FIXED
mozilla63
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox61 --- unaffected
firefox62 --- unaffected
firefox63 --- fixed

People

(Reporter: soeren.hentzschel, Assigned: Paolo)

References

Details

(Keywords: regression)

Attachments

(3 files)

Attached image screenshot
Bug 1473521 caused a regression in the add-ons manager. Please see the attached screenshot.

STR:

1. open the add-ons manager
2. press the "remove" button on one add-on
Clicking a category on the left and then go away with the cursor showing it with highlight colors is also a result of loading the richlistbox.css as a document stylesheet.
Thanks for filing the bug report! I have patches to adjust the specificity of some rules that should solve both issues.
Comment on attachment 8990619 [details]
Bug 1474193 - Part 1 - Increase specificity of richlistitem rules for add-on items.

https://reviewboard.mozilla.org/r/255680/#review262490
Attachment #8990619 - Flags: review?(dtownsend) → review+
Comment on attachment 8990620 [details]
Bug 1474193 - Part 2 - Increase specificity of richlistitem rules for in-content categories.

https://reviewboard.mozilla.org/r/255682/#review262494
Attachment #8990620 - Flags: review?(dtownsend) → review+
Pushed by paolo.mozmail@amadzone.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/99dd457960a1
Part 1 - Increase specificity of richlistitem rules for add-on items. r=mossop
https://hg.mozilla.org/integration/mozilla-inbound/rev/140937d55bd0
Part 2 - Increase specificity of richlistitem rules for in-content categories. r=mossop
https://hg.mozilla.org/mozilla-central/rev/99dd457960a1
https://hg.mozilla.org/mozilla-central/rev/140937d55bd0
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Verified that both issues are fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.