Closed
Bug 2057172
Opened 1 month ago
Closed 1 month ago
[Nova] Container tabs are hard to recognize
Categories
(Firefox :: Containers, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 2058198
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox153 | --- | unaffected |
| firefox154 | --- | unaffected |
| firefox155 | --- | affected |
People
(Reporter: mercichao, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
48.89 KB,
image/png
|
Details |
In version 155, the line for container tabs has been shrunk to 12px and positioned very close to the site icon. This makes container tabs difficult to recognize. Previously, the line was clear and visually outstanding, but now it blends with the site icon, especially when the colors are similar, reducing usability and clarity.
| Reporter | ||
Updated•1 month ago
|
Blocks: nova-chrome
See Also: → 2039854
Comment 1•1 month ago
|
||
Thanks for the report, Merci chao. The containers team is taking in feedback about this recent change.
Component: Sidebar → Containers
status-firefox153:
--- → unaffected
status-firefox154:
--- → unaffected
status-firefox155:
--- → affected
status-firefox-esr115:
--- → unaffected
status-firefox-esr140:
--- → unaffected
status-firefox-esr153:
--- → unaffected
Keywords: regression
Regressed by: 2054407
Comment 2•1 month ago
|
||
:baku, since you are the author of the regressor, bug 2054407, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Flags: needinfo?(amarchesini)
Comment 4•1 month ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•1 month ago
|
Status: NEW → RESOLVED
Closed: 1 month ago
Duplicate of bug: 2058198
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•