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
CustomTable > .datatable--even-row {background: red} was not effecting a background change.
The newly added :dark pseudo-selector had to be used: CustomTable:dark > .datatable--even-row {background: red}
The Issue: Documentation does not show this.
In the documentation (at least for DataTable) there is the COMPONENT CLASSES section. But there is no mention on the page about a :dark pseudo selector.
From only reading the documentation, someone would interpret that the selector .datatable--even-row would be sufficient for changing the color. This is not the case.
In reality, there could be other things affecting the default use of component classes.
Suggestion:
In the DataTable COMPONENT CLASSES section there is a table of descriptions. Maybe a change like this is good:
#old:
datatable--even-row Target even rows (row indices start at 0).
#changed:
datatable--even-row Target even rows (row indices start at 0). :dark pseudo-selector is used by default.
# or, ":dark pseudo-selector is applied"
# or, ":dark pseudo-selector is required"
I suspect there are other widgets that have the same issue.
The text was updated successfully, but these errors were encountered:
This is a follow up issue to an issue discussed and resolved on discord.
A quick summary:
CustomTable > .datatable--even-row {background: red}
was not effecting a background change.The newly added
:dark
pseudo-selector had to be used:CustomTable:dark > .datatable--even-row {background: red}
The Issue: Documentation does not show this.
In the documentation (at least for DataTable) there is the COMPONENT CLASSES section. But there is no mention on the page about a
:dark
pseudo selector.From only reading the documentation, someone would interpret that the selector
.datatable--even-row
would be sufficient for changing the color. This is not the case.In reality, there could be other things affecting the default use of component classes.
Suggestion:
In the DataTable COMPONENT CLASSES section there is a table of descriptions. Maybe a change like this is good:
I suspect there are other widgets that have the same issue.
The text was updated successfully, but these errors were encountered: