Closed
Bug 1397359
Opened 7 years ago
Closed 7 years ago
Title on "more" page for add-ons is not bolded
Categories
(Toolkit :: Add-ons Manager, defect, P3)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
FIXED
mozilla57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: andy+bugzilla, Assigned: mstriemer)
References
Details
Attachments
(4 files)
On the latest nightly, if I go to about:addons, then click on more for an add-on, the title isn't bolded. Attached screenshots of nightly and release.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8907770 [details]
Bug 1397359 - Larger add-on title in about:addons detail
https://reviewboard.mozilla.org/r/179448/#review184626
Attachment #8907770 -
Flags: review?(rhelmer) → review+
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/56a78e06eff8
Larger add-on title in about:addons detail r=rhelmer
Keywords: checkin-needed
Comment 6•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
Comparing the Firefox 56.0.2 (20171024165158) with Firefox 58.0a1 (20171112220346) under Wind 7 64-bit, I can’t see the difference between these two builds.
Could you tell me please, at what should I be looking?
Thanks in advance!
Flags: needinfo?(mstriemer)
Assignee | ||
Comment 8•7 years ago
|
||
There shouldn't be a difference, this was a regression where the title got smaller.
Flags: needinfo?(mstriemer)
Since there is no visual difference, is manual testing still required?
In case it doesn’t, could you please add the qe-verify - flag.
Thanks!
Flags: needinfo?(mstriemer)
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(mstriemer) → qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•