anchor.diff:  * It could happen that 2 tabs will share the same windowId for 1 request
   because the `LAZY` mode will check lazily, after rendering the view, if
   the windowId matches the `window.name`. Therefore it could happen that
  -@ViewAccessScoped or other scopes will unintentionally be destroyed.
  +scopes, which are based on the window handling (@ViewAccessScoped, @WindowScoped and @GroupedConversationScoped),
  +will unintentionally be destroyed.
   
   
   ===== Workflow Example
  
positive.code: also got rid of this flickering by storing away a 'screenshot' of the
  first page in onclick() and immediately restore this 'screenshot' on the
  intermediate windowhandler.html page. Technically we do this by storing
  away the and css information into the html5 localStorage and restore them on the
  intermediate page. We also introduced a WindowConfig which is able to
  parse a request and decide upon the UserAgent or any other information
  if a client will get an intermediate page or if he gets the result page
  
negative.code:     {
          return false;
      }
  
      @Override
      public boolean isClientWindowStoreWindowTreeEnabledOnButtonClick()
      {
  