The ace:tabSet component allows for static and dynamic caching of tab content. But the existing policy is a little limited, of either always being dynamic or always being static. For example, when a statically cached tab is the current tab, then it still will still be static, so input components won't get to render any new values that the user had just entered. As well, when using dynamic caching, even the non-active tabs render their non-visible contents. So we should probably come up with several different policies that applications may choose between.

An attempt to make static automatically change to dynamic, when it's the active tab, failed, since the old dom contents were no longer there to difference against, so it resulted in completely uncaching the tab. So, once you go static, you only want to go dynamic if you plan on updating that tab's content completely.

cacheMethod:
  none
  dynamic
  static
  dynamicRevertStatic
  staticExceptDynamicWhenChildPostback

If a static tabPane wants to temporarily switch to being dynamic, for just the current iifecycle, then there's a bunch of boilerplate code that the application has to write to manage that one-off switch and revert of the setting. We could instead add an edge policy such as dynamicRevertStatic, which would cause the tabPane component to temporarily behave as dynamic, but the itself switch the property back to static when done the current lifecycle's processing.

When a tabPane is statically cached, but has input or command components in it, then we need a policy to make it dynamic only when the child input or command component has done a postback, which would be the staticExceptDynamicWhenChildPostback mode.