Mateusz Paprocki

I suppose with `height_policy="fit"` (or `"max"`) or `"fixed"` with sufficiently large `height`, there could be room for single axis alignment.

It also sometimes shrinks back to the correct size. The layout is correct in this case, but slider's CSS is implemented in a way that's incompatible with the layout's way...

Add regression tests for: - [ ] #12123 - [ ] #8847 (if not covered by other tests)

This happens because `TileRenderer` manipulates ranges outside the scope of the default range management scheme. However, that happens only once, during initialization of a `TileRenderer`, so any updates to a...

This may be already fixed in PR #8085.

Also make sure to tab headers' scroll doesn't jump around after modifying tabs, especially after closing tabs (PR #8732).

Setting `Tabs.width` works, at least in this particualr case, which can be visualized by setting `Tabs.background`, e.g.:  `{min,max}_{width,height}` aren't fully implemented, so they are destined to fail.

> Ah yes, this is true, but seemingly the tab header does not span the full width: That may be just a CSS quirk.

Note also that a lot depends on the sizing policies/modes of all layout items involved, so we may need to speak about each suspicious complex layout individually. This is all...

Actually the header is clearly broken, because it shouldn't show scroll buttons in this scenario.