Dash - Connected filter buttons (decade, size) need visual tweaks
Bug #897627 reported by
Andrea Cimitan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
Won't Fix
|
High
|
Unassigned | ||
Unity |
Won't Fix
|
High
|
Unassigned | ||
unity (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
UPDATE:
The connected buttons were updated, and they look better.
The issues now are in the selected elements: Mirco and Andrea are aware of the issues.
If you select more than one element, the line between the selected items is different from design. Furthermore, the corners of the selection (2px wider) are not rounded but they have a clear cap.
The screenshot in comment #1 is no longer valid
ORIGINAL:
Unity 3P "Pixel-Perfect Precise".
Visual glitch number 4 in the screenshot.
The filter connected buttons have fuzzy edges/borders
tags: | added: unity3p |
Changed in unity: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
summary: |
- unity 3P - visual bug #6 + Dash - visual bug #6 |
tags: | added: udp |
Changed in ayatana-design: | |
assignee: | nobody → John Lea (johnlea) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in unity: | |
milestone: | none → backlog |
summary: |
- Dash - visual bug #6 + Dash - Connected filter buttons (decade, size) need visual tweaks |
Changed in ayatana-design: | |
status: | Triaged → Fix Committed |
Changed in unity: | |
status: | Confirmed → Triaged |
importance: | Low → Medium |
description: | updated |
tags: | added: top5p |
Changed in ayatana-design: | |
importance: | High → Critical |
tags: | added: euv |
Changed in ayatana-design: | |
importance: | Critical → High |
Changed in unity: | |
importance: | Medium → High |
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
Changed in unity (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in unity: | |
milestone: | backlog → none |
To post a comment you must log in.
Is this any more an issue or should this bug be closed?