Table: active <tr> fix

[louismaximepiton]

Fixes #33913.
May close #35158.

Based on ffoodd's idea.

Live preview

Solutions

Commits can be split.

• To allows .active on hoverables rows, I tried to implement Bug - tr background color for table-active when used with table-striped #33913 (comment). The main issue was the nesting thing, but seems to be fixed by setting the used variables to initial.
• The second commit is to fix nested tables background. For example with a .table-dark on the first table, on main is:
  

On preview is:

• The third one is just a typo error inside the doc.

Checks

• No regression on table page and surroundings. Couldn't spot any but haven't dig too much.
• No regression on table variants. Couldn't spot any but haven't dig too much.

[mdo]

Love the approach, but renaming CSS variables is a breaking change I think. We could keep this for v6, or we could try to address that and ship in v5.3. Thoughts?

[louismaximepiton]

IMO, it should be in v5 since folks can't have an .active cell or row inside a striped table.

I put this PR in draft since it requires more work to make it smoother for users but I don't think that we are changing variables with this PR (apart the accent one), we are adding some of them since previous variables will still be usable + I've seen a regression on striped tables that would be declared with a --bs-table-bg, they aren't striped anymore. I'll try to check that asap!

EDIT: I'll try to make no breaking change with the actual variables.

[louismaximepiton]

I think this version is way better since we don't rename the actual variables, we just introduce more of them. Furthermore, you can still give a special color by overriding the associated CSS var, it'll still continue to work correctly.

I can't see any regression atm, shall I set this PR as open for 5.3.0?

[mdo]

Fixed the syntax to match our variables everywhere else, but with the main merge we have a bundlewatch issue. Can you take a pass to update @louismaximepiton?

[XhmikosR]

@louismaximepiton can you rebase please?

[tkrotoff]

This is a breaking change.

Table background has been transparent since 2012

Also table-primary & table-secondary are available but not table-tertiary, why?

@louismaximepiton

[louismaximepiton]

Hey, thanks a lot for your feedback!

I think I changed the default background from transparent to var(--bs-body-bg) because the nesting tables was broken if I remember well. I'm not sure how to handle this. If you have any other idea please don't hesitate to add a PR.

For .table-tertiary, it doesn't exists yet since our components (buttons, list-group, ...) don't have such a variant. I think if it's done for one, it might be done on all sides at the same time.

[julien-deramond]

Confirming the part regarding the table variants. It's mentioned in our Tables > Variants documentation:

Heads up! Because of the more complicated CSS used to generate our table variants, they most likely won’t see color mode adaptive styling until v6.