You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Dark styled text is unreadable: Black and any other colour that has low contrast against dark background such as this dark purple bullet
Dark mode doesn’t switch text from black to white if the font colour is not set to “automatic” in the style
Dark mode doesn’t invert text colour even if the font colour is set to ‘automatic’ in the cases where the text is above a shape that is black or the page/slide has a black background we still end up with unreadable text. A fix is on its way 165024: ONLINE: Set automatic fontcolor according to background color: https://gerrit.libreoffice.org/c/core/+/165024.
Dark mode doesn't affect slide show2
Dark mode doesn’t invert text colour in relation to character highlight colour. A text set to ‘automatic’ font colour and white highlight doesn’t get inverted when the user switched from light to dark mode →
Unable to switch mode selectively. There are cases where user would like to switch off dark mode for document only when the dark mode is on. Examples: Wants to colour/print proof simulate; Needs to check how the document will look like before exporting; Wants to edit document while making sure the company branding guidelines are being followed. There is some initial steps in the works config: remove scheme document background colors #8564: config: remove scheme document background colors #8564
Allow dark mode for the UI to be disabled
Integrator that have their very own custom UI (for example always dark) are unable to toggle between dark and light mode in the document only so they can have more control over how their customizations and UI are handled.
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.
The text was updated successfully, but these errors were encountered:
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.
Default automatic colour styles in nextcloud writer #3494
: Default automatic colour styles in nextcloud writer nextcloud/richdocuments#3494165024: ONLINE: Set automatic fontcolor according to background color
: https://gerrit.libreoffice.org/c/core/+/165024.config: remove scheme document background colors #8564
: config: remove scheme document background colors #8564Context
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.
The text was updated successfully, but these errors were encountered: