If it works for you, then I’d say “don’t try to fix something that isn’t broken”
Your rule should apply to both source and preview view. You’ll face these questions only if you plan to create a big theme, otherwise there’s no need to bother yourself
It does not exactly work right … not in all situations. They work for some but not all, which is why I was wondering if there is a better way to do it.
There is quite a bit of CSS classes involved with a table (as I see in the dev tools). If I understand correctly, there are different classes for rows, columns and such. I am not an expert to choose an uber way that just works.
Eventually use !important after red but before ;
This way you’ll force red, but I’d rather discourage to use important to lightly. If several important conflict each other nothing gets rendered.
Or you build a unique table, but then you’ve to add table-a to your cssclass yaml header.
No, usually i don’t use html tags, because cumbersome to read and insert, imo.
At first, I used html tags too (quickadd to the rescue) but later, I switched over to css and didn’t look back.
I used the definition unique because with cssclass you’re able to add standalone tables, at last in my experience.
If you’re interested in rich table layout, get a copy of my theme Dune from Obsidians theme repo. It covers colored tables and much more