@jaredwhite Unfortunately, that only seems to order individual items - the way the Windows implementation works is that the entire row which *contains* the item is moved, but the item remains within the same position within that row.

(Just moving the active item to the first position would not be great UX-wise; it could very easily look like selecting the item did nothing, because the first item always remains selected, and there's no 'muscle memory' that can be built of where a tab is relatively located)

@keithjgrant Flexbox is not a hard requirement; if it can be done with grids in a sensible manner (eg. it doesn't make tabs look weird) then that's totally fine too, as long as the tabs themselves can still be specified as a sequence of auto-sized items (ie. not needing to manually split tabs across lines).

Not sure I understand what you mean with a 'custom property' here though?

@joepie91 aka CSS variable (https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties)

@keithjgrant Ah, right. I'm not sure how I would apply that to this problem, though?

The only implementation I can think of would be to give each line its own variable (containing ordering values) and then adjust those variables based on selection - but that would still require JS to update on tab selection, as well as manual line specification...

@joepie91 I was picturing some sort of ‘:has(:active)’ check, but I haven’t exactly thought through all the specifics

@keithjgrant Ahhh, I see what you mean. I think that would only work if there were a per-line container element, which I think is only possible when manually specifying lines? Or is there some way to automatically spawn a pseudo-element per line or so? I haven't quite gone this far into the weeds with grids before :p