Skip to content
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

A better dark mode #9059

Open
11 of 13 tasks
pedropintosilva opened this issue May 15, 2024 · 2 comments
Open
11 of 13 tasks

A better dark mode #9059

pedropintosilva opened this issue May 15, 2024 · 2 comments
Labels
bug Something isn't working dark-mode

Comments

@pedropintosilva
Copy link
Contributor

pedropintosilva commented May 15, 2024

First things first: For everyone who has been following CODE release, testing it, reporting bugs and overall helping. Thank you!


Hi all, I'm creating this issue to leverage all the valuable feedback that the community has been sending and hopefully lay out the plan towards a better dark mode.

Plan and the issues it fixes

Here are the main issues we are been tracking closely by order of importance.

Context

Fixing user's documents seems impossible for a few reasons and even if it was possible it sounds based on a poor premise: would we be really fixing it? I can think of a few cases where that would not result in the expected output while taking the control from the end user. Thus, it seems to me that the right approach is to bite the bullet and just go ahead and implement #9060. This will fix the overall experience. The other issues are of a less importance but still good to track them.

@Ornanovitch
Copy link

Hey there!

Lately I've been thinking again about all these dark theme stories. I am convinced of the way you want to solve the problem in general (dynamic document color inversion), but I have to say I still don't understand the overall strategy.

We have two dark mode levels: the ui dark mode and the document dark mode. The first one is mature, it's even lovable! People who appreciate dark mode do want to use it. The second one has many (small but real) problems that makes it objectively an experimental feature.

While you have these two completely different maturity states for two different features, you persist to make the less mature one on by default when one could just want the mature one. And then you develop a button to disable the problematic experimental feature (invert background) for those who want a mature and basic dark mode (just the ui).

I feel this way of deploying dark mode is counter-intuitive: you already have a good ui dark mode, why not let users benefit from it easily, intuitively? And for those who really want a document color inversion (which is not systematically nor strictly a dark mode IMO), the "invert background" button could be used (but it should be renamed: "invert document colors (experimental)".

I hope you understand my point of view. I really like CO's work, I just want to help with some UX thoughts that I've been thinking about for a long time...

@jancborchardt
Copy link

Looking at this related longer standing issue from our side, it looks like a lot of items are already resolved as well – right @pedropintosilva?

@jancborchardt jancborchardt moved this from 🏗️ At engineering to 🎉 Done in 🖍 Design team Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dark-mode
Projects
Status: No status
Development

No branches or pull requests

4 participants