Hello @Rafaelcjr!

Not a Sencha aspect. This didn't make it to changelogs/breaking changes because this setting was not supposed nor expected (back then at least) to be changed on-the-fly like you do -or- it could have just been overlooked, by accident.

The behavior is Ext.NET-specific and as mentioned above was introduced in the first Ext.NET v2 releases. Back then, this change possibly slipped unwritten as your use case scenario was not really expected or anticipated by us.