-
Notifications
You must be signed in to change notification settings - Fork 846
Opt in dark mode support is actually not opt in #1226
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
Comments
This was fixed here: #1224 |
I hope so. release is not tagged yet. will find out later if it did indeed fix the issue or not. |
That won't fix this particular issue. The problem is that existing users of the Livewire stack often won't have published views. After updating, they'll now be using views with dark classes.
This is correct, but I don't think it's something people will know about or should have to do. At this stage, the only solution I can think of is to revert the dark mode changes. We could then either:
|
Hey @ziming, we've reverted the dark mode changes for now. The issue should be resolved when you update to Jetstream |
Description:
I originally commented in with screenshots proof. But thought i should create an issue instead as that is a closed PR and it is likely nobody sees it
#1209 (comment)
But tldr, I installed jetstream months ago, composer update this morning and tonight my jetstream sites all look very weird with some components dark and some components white.
So it looks like it is actually not opt in as I never ran the jetstream:install --dark command since my installation of Jetstream is months ago, not today.
All I did is a composer update, nothing else.
The text was updated successfully, but these errors were encountered: