Skip to content

Conversation

@nickvergessen
Copy link
Contributor

Before After
Background is not our background color and therefor also used in dark mode background is our color variable so perfectly fine in dark mode
grafik Bildschirmfoto vom 2023-05-10 09-57-25
Bildschirmfoto vom 2023-05-10 10-08-40 Bildschirmfoto vom 2023-05-10 10-09-31

@nickvergessen nickvergessen added bug Something isn't working 3. to review Waiting for reviews feature: select Related to the NcSelect* components accessibility Making sure we design for the widest range of people possible, including those who have disabilities labels May 10, 2023
@nickvergessen nickvergessen added this to the 8.0.0 milestone May 10, 2023
@nickvergessen nickvergessen self-assigned this May 10, 2023
@nickvergessen
Copy link
Contributor Author

Found while fixing nextcloud/server#38170

Copy link
Contributor

@Antreesy Antreesy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦭

--vs-state-disabled-color: var(--color-text-maxcontrast);
--vs-state-disabled-controls-color: var(--color-text-maxcontrast);
--vs-state-disabled-cursor: not-allowed;
--vs-disabled-bg: var(--color-background-dark);
Copy link
Contributor

@Antreesy Antreesy May 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aliases --vs-state-disabled-* should update this value, but maybe it's not hapenning because of the css rules order, so I guess, it's legal to override here

@nickvergessen
Copy link
Contributor Author

/backport to stable7

Comment on lines +948 to +950
--vs-disabled-bg: var(--color-background-dark);
--vs-disabled-color: var(--color-text-maxcontrast);
--vs-disabled-cursor: not-allowed;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 the --vs-state-disabled-* variables are already set above and are aliased to these variables internally https://github.com/nextcloud-deps/vue-select/blob/9294fdcbf39380fd5cc766144b18b6f86cf107f4/src/css/global/states.css#L13C35-L15

Is this solvable without adding non-publicly documented variables https://vue-select.org/guide/css.html#available-css-variables-3-18?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no clue why, but it fixes it. As per #4079 (comment) it could be the order, since --vs-disabled-bg: var(--vs-state-disabled-bg); is not a permanent redirect, but it writes the currently value of the second var into the first one. So maybe we only replace the --vs-state-disabled-bg after that and therefore also need to overwrite the first var

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this happens because:
--vs-disabled-bg: var(--vs-state-disabled-bg); from vue-select if on the :root selector.

And our --vs-state-disabled-bg: var(--color-background-dark); is on the body selector.

So when --vs-disabled-bg is set, the --vs-state-disabled-bg variable holds the old value.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I think it has the same cause as this one: nextcloud/server#36462

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews accessibility Making sure we design for the widest range of people possible, including those who have disabilities bug Something isn't working feature: select Related to the NcSelect* components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants