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
When Use system color scheme (Settings > Appearance > Themes) is enabled and Standard Notes is passcode locked (Settings > Security > Passcode lock), the Standard Notes theme does not change with the system theme while the application is locked. This creates a visually undesirable effect where the Standard Notes application window is in a different color theme from other application windows that may be open while Standard Notes is not in use, until it is unlocked.
Steps to reproduce the behavior:
Go to Settings > Appearance > Themes and enable Use system color scheme.
Go to Settings > Security and enable Passcode lock.
Lock the Standard Notes application.
Go to system settings and toggle the color theme between light and dark.
Notice that the Standard Notes theme doesn't change
Expected behavior
The Standard Notes theme should change with the system theme when Use system color scheme is enabled, even if Standard Notes is currently locked with Passcode lock.
Desktop:
OS: macOS Sequoia 15.2
Standard Notes Version 3.195.13
The text was updated successfully, but these errors were encountered:
When Use system color scheme (Settings > Appearance > Themes) is enabled and Standard Notes is passcode locked (Settings > Security > Passcode lock), the Standard Notes theme does not change with the system theme while the application is locked. This creates a visually undesirable effect where the Standard Notes application window is in a different color theme from other application windows that may be open while Standard Notes is not in use, until it is unlocked.
Steps to reproduce the behavior:
Expected behavior
The Standard Notes theme should change with the system theme when Use system color scheme is enabled, even if Standard Notes is currently locked with Passcode lock.
Desktop:
The text was updated successfully, but these errors were encountered: