This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
no tab close icon is shown for the active tab on Windows #10123
Milestone
Comments
I think it will be fixed by the same fix as #9872 and that fix will also help some users that have tear off sensitivity problems. |
@bbondy is there a specific DPI you're using for this? I'm not able to reproduce the issue at 125% (maybe I'm not doing the correct steps). What I'm trying:
This is using 0.19.x and Muon 4.4.x |
I see this on my surface book and desktop which are both set to 150% DPI |
OK reproduced 😄 Here are the steps!
|
after above comment this seems related to tab breakpoints so I'm taking this one |
cezaraugusto
modified the milestones:
0.20.x (Developer Channel),
0.19.x (Beta Channel)
Aug 22, 2017
ghost
added
the
sprint/1
label
Sep 13, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 14, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 14, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 15, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 15, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 19, 2017
syuan100
pushed a commit
to syuan100/browser-laptop
that referenced
this issue
Nov 9, 2017
- tabs can now respond beautifully to intersections - Also BEMify tabs Auditors: @bsclifton, @luixxiul fix brave#6716 fix brave#7301 fix brave#7730 fix brave#7765 fix brave#7925 fix brave#10123 fix brave#10509 fix brave#10544 fix brave#10582 fix brave#10611 fix brave#10838
35 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10691 (comment)
Active tab should show close icon always on hover for default tabs and always visible for small tabs.
Reported by @bbondy and seems like a DPI issue/Windows specific. May be related to #9779 and across platforms. Moving both to 0.18.x as this makes tabs almost unusable.
The text was updated successfully, but these errors were encountered: