Closed
Bug 1457303
Opened 8 years ago
Closed 8 years ago
Thick border around autocomplete popups in Modern theme.
Categories
(SeaMonkey :: Themes, defect)
SeaMonkey
Themes
Tracking
(seamonkey2.49esr fixed, seamonkey2.53 affected, seamonkey2.57esr fixed, seamonkey2.58 fixed)
RESOLVED
FIXED
seamonkey2.58
People
(Reporter: frg, Assigned: frg)
References
Details
Attachments
(2 files, 1 obsolete file)
|
46.67 KB,
image/jpeg
|
Details | |
|
1.94 KB,
patch
|
frg
:
review+
iannbugzilla
:
approval-comm-beta+
iannbugzilla
:
approval-comm-esr52+
|
Details | Diff | Splinter Review |
There is a thick border around autocomplete popups in the modern theme only which looks ugly.
| Assignee | ||
Comment 1•8 years ago
|
||
Patch for 2.49 from Matt A. Tobin with permission via irc to use it.
| Assignee | ||
Comment 2•8 years ago
|
||
The patch from Matt A. Tobin resolves the issue and applies clean to all current trees.
[Approval Request Comment]
Regression caused by (bug #):
User impact if declined: ugly styling
Testing completed (on m-c, etc.): c-esr52 c-r (2.53)
Risk to taking this patch (and alternatives if risky): cosmetic only
String changes made by this patch: --
Attachment #8971407 -
Attachment is obsolete: true
Attachment #8972113 -
Flags: review+
Attachment #8972113 -
Flags: approval-comm-esr52?
Attachment #8972113 -
Flags: approval-comm-beta?
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/7d3b933e58cb
Fix autocomplete thick border styling in SeaMonkey Modern theme. r=frg DONTBUILD CLOSED TREE
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•8 years ago
|
status-seamonkey2.58:
--- → fixed
Target Milestone: --- → Seamonkey2.58
Comment on attachment 8972113 [details] [diff] [review]
1457303-autocompleteModern.patch
a=me
Attachment #8972113 -
Flags: approval-comm-esr52?
Attachment #8972113 -
Flags: approval-comm-esr52+
Attachment #8972113 -
Flags: approval-comm-beta?
Attachment #8972113 -
Flags: approval-comm-beta+
| Assignee | ||
Comment 5•8 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•