Replacing existing colors with npm module, and refactored Sass #2045
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#2045
Loading…
Reference in a new issue
No description provided.
Delete branch "redesign"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR is unfinished, still have to go through the app and tweak.@ -100,17 +100,15 @@ class WunderBar extends React.PureComponent<Props> {
if (suggestion) {
if (suggestion.type === 'search') {
onSearch(query, resultCount);
} else if (isURIValid(query)) {
The linter changed this file, not me.
Pretty sure this needs fixing.
This is looking great. I really like the new font. I found a few issues and also have a few more generic comments.
I'm not super sure about the new green color. I like the actual color but it's a lot harder to read buttons with white text. The contrast ratio is significantly lower than the previous combination which was already pretty low.
https://webaim.org/resources/contrastchecker/
We can remove this now
@seanyesmunt Pushed up some changes. The
$lbry-teal-5
color (#2f9176
) is being used for all buttons now, due to its excellent contrast. It doesn't pass WCAG AAA though, only WCAG AA.#1f614d
passes all tests but it's also pretty dark.@NetOperatorWibby I don't think we have to pass all,
teal-5
looks great. Way easier to read compared toteal-3
The search page is looking better on dark mode. There are still some issues with placeholders.
The input background color is also a little tough to read on dark mode (both search and copyable inputs)
And the markdown input on the publish page
Alright, fixed inputs. Found a rather interesting bug/feature. When you highlight text and then switch themes, the selected text is white and will not fix itself unless you reload the app.
This is another good site for contrast testing: https://colorable.jxnblk.com/ffffff/2f9176
A few last issues (I think)
The startup screen/snackbar/text highlighting should use
teal-5
tooA few last issues (I think)
The startup screen/snackbar/text highlighting should use
teal-5
too@ -28,0 +108,4 @@
&.btn--header-publish {
background-color: $lbry-teal-5;
}
Not super sure if we need this but I think that was for specificity
@NetOperatorWibby After looking at some of the code more closely I'm starting to think we should keep the
vars
file. That would avoid the need for using nested rules in the dark theme scss file.Currently in some cases, if any layout changes, the dark mode would break.
@seanyesmunt We lose the flexibility of using
rgba
functions and end up having more colors than necessary. I don't think layout changes are a strong argument. Dark mode would have to be checked out if changes are made regardless.@NetOperatorWibby Ah I didn't know we couldn't use
rgba
functions with that. Ok I'm fine with it. 👍@seanyesmunt Do I need to do anything else to get this merged?
I think the only thing left I've noticed is the text in the search bar is really hard to read on light mode. After that is fixed I think we can merge this.
Done
I'm guessing there will be a few more things to fix before this is released but it's fine for now to begin testing.
Cool beans, I'll go through everything finely.