Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consume more tokens from arches theme, add dark mode toggle #91
base: main
Are you sure you want to change the base?
Consume more tokens from arches theme, add dark mode toggle #91
Changes from 9 commits
7e3bbaf
f811b9b
cfc70dc
9149cdf
ec29833
ad89307
81daf62
2979f72
b5aaa35
7ba76f7
8b764d5
abdb414
822246c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change, there's now a difference (on my local browser) between semibold and bold. (sans-serif in my browser was lacking a weight value for 600). Which means: we can preset the font weight for button labels to 600/semibold without it being too loud (it was looking the same as bold)
Then we'll have a default for button labels that looks good both in the controlled list manager (arches chrome) and here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eh I'd say remove
system-ui
, as that varies from system to system and pulls us away from a unified experience. https://infinnie.github.io/blog/2017/systemui.htmlThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw that also, but I can't remember if I saw that before or after I made this addition, 😄 . I'll back it out. You have a good point we're building a unified experience, not a blog for a law office.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isDarkModeEnabled
works! (🎉 ). However, regardless of if its value, the theme when the page is loaded is always light. I was able to solve this locally viaHowever, this may not be the right solution. There's further complexity to add that may nullify that pattern. Namely, I can set the toggle to
dark
, see the change, refresh the page, and it's automatically set back tolight
. My guess is that either cookies or localstorage need to be leveraged to persist this through page refreshes.If we wanted to get really fancy we could add a column to the
User
model to support preferred theme, but that's probably overkill at this point. And we'd still need something on the browser to persist for anonymous user so /shrug that's not an entirely baked idea.If this component is changed to read from cookies/localstorage on mount, it'd be more readable to change the toggle method to accept an arg so it can be explicitly set the mode. This will also support adding other themes later. However I'm not married to this pattern, YAGNI and whatnot /shrug. Regardless, reading from cookies/localstorage nullifies the simple code laid out above.
But this reveals another titchy thing: we're handling all of theming in this component. If I have a cookie ( or bit of localstorage ) saved that says I prefer dark mode, I'd expect the application to handle this regardless of the presence or absence of the header / DarkModeToggle. Like in reports and whatnot. It could be argued that the ability to switch themes should be handled in this component of course, but the ability to query a preferred theme and apply it should be handled at a deeper level.
Perhaps even in core since it's touching the
<html>
element, but I don't feel strongly about that yet.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wanted to deemphasize these buttons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without using the label prop, it wasn't using the tokens for button label font weight (not noticeable until I started overriding that weight via the theme)