Hi,
ah, ok ?? Thanks for clearing this up ?? Initially, I’d thought that the actual saving is not working, and not the visual results.
The reason that the Custom CSS is not overriding the default CSS usually is a something like a “conflict”. This means that there are two (or more) CSS commands that try to change the same property on the same elements. These commands don’t need to come from the Custom CSS or default CSS though. They could also come from the theme’s CSS for example, as many themes contain CSS code to style tables.
Usually there are two major ways of settling these conflicts: You would either have to make the CSS selector more specific (i.e. the .wp-table-reloaded-id-....
part), by instead using CSS/HTML IDs instead of CSS classes, or you can try to raise the priority of a given command (this usually is quicker and easier), by adding the !important
keyword.
Example:
If some CSS like
.wp-table-reloaded-id-123 td {
background-color: transparent;
}
does not result in a change,
.wp-table-reloaded-id-123 td {
background-color: transparent !important;
}
will likely do.
This example shows another possibility on why (in the example) the background color does not change: The CSS only changes the background color of the actual cells to transparent. However, the actual rows (which you can imagine as a layer below the cells), or even the table itself, can still have a background color that is different to the page’s background color.
I hope that this explanation was not too confusing ??
Regarding not loading the default CSS:
This basically will only “hurt” if you actually have a table on the page, that shall have the default styling (i.e. the default color set, default fonts, and probably some borders). If you are overriding the CSS of all tables with custom styling anyway, removing it is no problem.
Best wishes,
Tobias