Changes between Initial Version and Version 1 of Ticket #3442


Ignore:
Timestamp:
Jun 16, 2007, 3:11:51 AM (13 years ago)
Author:
Dustin Machi
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3442

    • Property Owner changed from anonymous to bill
    • Property Component changed from General to Dijit
  • Ticket #3442 – Description

    initial v1  
    11Multiple requests to show a content pane can cause the page to load from the server more than once. This comes about in a fairly common case of placing a few content panes in a container (my test uses page container)and then showing any one of them at a time. When the page loads each of the hrefs for each content pane is loaded as expected.  When the PageContainer initializes it selects one of the widgets (the first one).  Since the page has already been loaded, i expect it to just go to that page.  The actual behavior is that it loads the page again.  When these pages contain widgets it causes them to be parsed,created,destroyed,parsed created   in a small period of time and in some cases can have other adverse affects in an app. Subsequent switching of the page uses the cache normally.  I expect this error to be somewhere in the area of not aborting the original request properly when the next one came along.
     2
     3Putting in a delay of course works around this issue when the developer is selecting a child (for example, in the test file below if you put a setTimeout of 300 ms, it will let the first one complete and the second one will be served from cache.  However, since the page container shows one by default (and presumably tab container and the other containers do as well), avoiding this double load is not possible in this circumstance
    24
    35Test Page: