Hide
Today when we apply a customization change in SessionChangeManager, we check if this request is a postback or not. If it is, then we will assume that it's state has been restored correctly, and we will skip. This works for normal views, but for views with a included sub page, like a region, we can't restore the state correctly, and since it's a postback, we will skip applying the customizations, so the end result is we will lose the customizations.
The current fix is to always return false in _isStateRestored(). In the long term, we might have better solutions like asking all page fragments to restore their states.
Show
Today when we apply a customization change in SessionChangeManager, we check if this request is a postback or not. If it is, then we will assume that it's state has been restored correctly, and we will skip. This works for normal views, but for views with a included sub page, like a region, we can't restore the state correctly, and since it's a postback, we will skip applying the customizations, so the end result is we will lose the customizations.
The current fix is to always return false in _isStateRestored(). In the long term, we might have better solutions like asking all page fragments to restore their states.
Bug
Major