Closed
Bug 662378
Opened 15 years ago
Closed 14 years ago
"Arrow Panel" displays a line between the arrow and the box that shouldn't be there
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: zer0, Assigned: zer0)
Details
Attachments
(2 files)
See the snapshot. It's probably depends by the fact that the "arrow panel" is also transparent, so the arrow display a bit the shadow that surround the box.
Updated•15 years ago
|
Priority: -- → P3
Target Milestone: --- → Future
| Assignee | ||
Comment 1•15 years ago
|
||
The behavior is caused by the box-shadow property used to create a sort of "emboss" effect on the panel.
Because both arrow and panel are transparent, when the arrow use a negative margin of 2px to overlap the box, the section overlapped results more darker: that creates the line displayed in the snapshot.
A quick fix could be just avoid the emboss, and use a negative margin of 1px instead of 2px, as showed in the second snapshot.
However, if we do that just in jetpack, it will change the look & feel of a panel compared to the regular Firefox's panel. Because in Mac OS X is not so evident, we can leave as is for the moment.
In Windows is more evident that in OS X, and because is related but not dependent by the same reason, I will open a different bug for that.
| Assignee | ||
Comment 2•15 years ago
|
||
Do you think this is worth the effort to figure out how/what to fix and fix it?
Whiteboard: [triage:followup]
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: Future → ---
Comment 5•14 years ago
|
||
Waiting on feedback from Matteo here
Assignee: nobody → zer0
Priority: P3 → --
| Assignee | ||
Comment 6•14 years ago
|
||
I'm sorry I forgot to add the discussion I had with Myk at that time. We ended up that is not worthy to fix it, and for sure is not something we should fix in jetpack.
Maybe it will be fixed in Australis.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Whiteboard: [triage:followup]
You need to log in
before you can comment on or make changes to this bug.
Description
•