Closed Bug 1340626 Opened 4 years ago Closed 4 years ago
Ugly border around dropdown buttons in UI
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170217094919 Steps to reproduce: run autoland win10/64 opt build: https://hg.mozilla.org/integration/autoland/rev/554a4f2a1523 Actual results: ugly border around "show your bookmarks" button Expected results: no ugly border around "show your bookmarks" button
possibly fallout from landing of bug 1340495 patch?
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Component: Untriaged → Theme
I tested using Fx 53.0a1 on Ubuntu and could not reproduce the problem.
Assignee: nobody → dao+bmo
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows 10 → Windows
Hardware: x86_64 → All
Richard feel free to steal this review if you want.
Comment on attachment 8838785 [details] Bug 1340626 - Remove fallback styling from dropmarker.css. https://reviewboard.mozilla.org/r/113590/#review115164
Attachment #8838785 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/91b0938bc976 Remove fallback styling from dropmarker.css. r=Paenglab
That seems to have fixed the issue.
4 years ago
Duplicate of this bug: 1340751
4 years ago
Has Regression Range: --- → yes
Has STR: --- → irrelevant
Summary: ugly border around "show your bookmarks" button (bug 1340495 fallout?) → Ugly border around dropdown buttons in UI
Duplicate of this bug: 1340868
I'm not sure if this is the same issue, but I don't think the dropdown button UI at about:addons looks the same as it did a couple days ago.
Just to add a screenshot to this bug report
Duplicate of this bug: 1341216
good news, we see a performance improvement with this change! == Change summary for alert #5219 (as of February 17 2017 23:56 UTC) == Improvements: 4% tresize windows8-64 opt 11.69 -> 11.21 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=5219
VERIFIED as fixed with Mozilla Firefox 54.0a1 (2017-02-21).
You need to log in before you can comment on or make changes to this bug.