Hey @mellerbeck -
This was actually an unintentional regression created during the performance improvements introduced in r260 and r261. Previously, this page loaded slow enough that incorrect load order was never exposed, but was with this page working faster, we ran into this new behavior.
We have addressed this in r262, which will be rolling out early next week.
Pete