-
Notifications
You must be signed in to change notification settings - Fork 94
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
Use the color-primary-element* variables #4178
Conversation
1 failed and 2 flaky tests on run #9824 ↗︎Details:
|
Test | Artifacts | |
---|---|---|
Test the rich text editor menu bar > word count > empty file |
Output
Screenshots
|
sync.spec.js • 1 flaky test
Test | Artifacts | |
---|---|---|
Sync > recovers from a lost connection |
Output
Screenshots
|
SessionApi.spec.js • 1 flaky test
Test | Artifacts | |
---|---|---|
The session Api > open the session > returns connection |
Output
Screenshots
|
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.
Thanks @szaimen! Shall we backport this to stable26 and stable25? |
Signed-off-by: Simon L <[email protected]>
4e785ba
to
815372a
Compare
/compile |
Feel free to but not doing so would be fine as well imo |
Let's keep this for 27 for now as I'm not fully sure we backported all recent adaptions of the css variables to those branches. |
Signed-off-by: nextcloud-command <[email protected]>
Explanation: the color-primary variables are not to be used in components because the introduce problems with high-contrast primary colors. Fix this by using the primary-element variables instead.