ubuntu dock border radius not matching icon focus border radius (using dconf-editor to change settings)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell-extension-ubuntu-dock (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When disabling the dock's full height and straight corner enforcement via dconf-editor, the border radiuses do not coincide and protrude from the inner focus highlight of the icon onto the dock's perimeter.
Although not necessarily supported by the official visual guideline (which aims to be Unity-like), all available features and options that can be customised or triggered by a user should be verified and tested for design consistency.
Solution:
The dock's icon highlight (focus) should have a higher border-radius value to accommodate the dock's corner rounding.
See attached image for detail.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 12:00:31 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | gnome-shell (Ubuntu) → gnome-shell-extension-ubuntu-dock (Ubuntu) |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- ubuntu dock border radius not matching icon focus border radius + ubuntu dock border radius not matching icon focus border radius (using + dconf-editor to change settings) |
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.