I'd say the rearranging of the tabs is a separate thing and not relevant to the specific change of exposing the property for storage, this should be split into multiple PRs IMO

@AThousandShips In TabBar moving the tabs array to be above is necessary for this pr so it loads in the correct order, or we would get an issue like #10213. If wanted I can add an explanatory comment like was done for that fix (#16739 (comment)), something like // "current_tab" property must come after "tab_count", otherwise the property isn't loaded correctly.

For the TabContainer's tab_alignment, that didn't need to be moved in this pr so I could split it into a separate pr or just not do it at all.

That would indeed be required, as you didn't mention it in the PR either

The rest should be separate to focus the review on just the issue

added the comment and undid the tab_alignment move.

Does it only have to be above the current tab? If so I'd say to move it instead, like the other PR did

I'd prefer as little changes as possible to solve the issue, generally the idea

In OptionButton the array is at the top of all properties, so that's what I did here. I didn't want to have the array in between the properties since it's cleaner when they're together, but I could since it only needs to be above current_tab.

Just make sure it doesn't affect any other properties (hence why moving only the relevant one is safer, and preferred)

It looks like no properties are affected by tab count and tab count is not affected by any other properties. _update_cache() and similar are either only called when not in the tree or or called everywhere they are affected, so the order doesn't matter for them.

made ensure_tab_visible run out of the tree so that it properly handles the saved current_tab.

Thanks!