Closed
Bug 1197062
Opened 9 years ago
Closed 9 years ago
Audio indicator position strange in dev edition theme on pinned tab
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jsantell, Unassigned)
References
Details
Attachments
(1 file)
12.53 KB,
image/png
|
Details |
When an audio indicator appears on a pinned tab with the dev edition theme, it's positioned strangely (see attachment).
Reporter | ||
Comment 1•9 years ago
|
||
STR: * Go to a tweet with a vine attached, or use this lovely link and pin the tab https://twitter.com/Babylonian/status/634461984499499008 * Notice the audio indicator crushed against the favicon
Updated•9 years ago
|
Blocks: tab-sound-indicator
Comment 2•9 years ago
|
||
What's strange about it?
Reporter | ||
Comment 3•9 years ago
|
||
When on a not pinned tab, it looks like an extension of a title, in this pinned tab attachment, it is pushed to the top, both off center and not aligned as fas as I can tell to anything, and generally looks like a CSS positioning error. I'm not sure what I'd expect, I'm not a designer, just "looks wrong", but maybe this is subjective
Comment 4•9 years ago
|
||
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #3) > When on a not pinned tab, it looks like an extension of a title, in this > pinned tab attachment, it is pushed to the top, both off center and not > aligned as fas as I can tell to anything, and generally looks like a CSS > positioning error. I'm not sure what I'd expect, I'm not a designer, just > "looks wrong", but maybe this is subjective I see a pretty similar result in the Default theme. In the Dev Ed theme it looks like the icon is maybe a bit more over the favicon, but I'd say it's in the same ballpark.
Comment 5•9 years ago
|
||
This is by design, according to the UX spec. The intention is for the icon to overlay the favicon, because we don't want to increase the tab width. The positioning of the icon is the same in both themes, fwiw. -> INVALID.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•