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
Tab Label Rendering Issue #9398
Labels
Milestone
Comments
jonathansampson
added
bug
design
A design change, especially one which needs input from the design team.
feature/tabsbar
OS/Windows
labels
Jun 12, 2017
I believe this is related to the general tab-rendering issue where labels are made up of transparent text, masking a gradient background. We need to move to using a pseudo-element to achieve the fade effect. This requires a little work considering we need to accommodate hovered, non-hovered, theme colors, non-theme colors, private tabs, and public tabs. |
@jonathansampson IIRC, these issues would also be resolved with that same fix:
|
@bsclifton I believe that is correct. |
@jonathansampson isn't this related to the improvement we talked last Sunday? if so I think you are very close btw. ++ for @bsclifton findings. If above is true I agree they'll be fixed by too. |
@cezaraugusto It is. I should have that wrapped up very soon. |
bsclifton
added
usability
and removed
design
A design change, especially one which needs input from the design team.
labels
Jul 19, 2017
ghost
added
the
sprint/1
label
Sep 13, 2017
syuan100
pushed a commit
to syuan100/browser-laptop
that referenced
this issue
Nov 9, 2017
- text w/ gradient can be buggy. Let's do it with a layer Auditors: @luixxiul fix brave#8414 fix brave#9398
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10691 (comment)
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Tab labels have an issue with rendering where previous values may not be cleared properly. As a result, this can paint two labels in the place of one.
Platform (Win7, 8, 10? macOS? Linux distro?):
Desktop (Windows?)
Brave Version (revision SHA):
0.16.9
Steps to reproduce:
TBD
Actual result:
Labels become unreadable.
Expected result:
Labels remain legible and clear.
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Is this an issue in the currently released version?
Yes
Can this issue be consistently reproduced?
Yes
Screenshot if needed:
The text was updated successfully, but these errors were encountered: