A post remembers how big it is. The size is worked out from the pieces standing beside it, as it always was, but the result is now left on the post's own saved object - so it opens at the size it really is rather than opening at the widest a post can ever be and settling down five seconds later. That guess was safe in the direction it was wrong in and still had three costs, all of which are gone: an unupgraded post showed two extra columns and a row on every zone load, a client that never owned a post held it at the maximum for as long as it stayed loaded and then shrank it under an open window, and turning
UpgradesEnabledoff did not stop any of it.
Discussion
Nothing said yet.
Sign in or make an account to join in.