Changes between Initial Version and Version 1 of Ticket #12550


Ignore:
Timestamp:
Mar 29, 2011, 3:35:58 AM (9 years ago)
Author:
bill
Comment:

Thanks, BTW you can and should register you email in trac, to get notifications.

Sounds like you are saying this is a regression from 1.5?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12550

    • Property Component changed from General to Dijit
    • Property Summary changed from dijit.layout.ContentPane - destroys contents on refresh even if href is "" to [regression] ContentPane: destroys contents on refresh even if href is ""
  • Ticket #12550 – Description

    initial v1  
    44All steps necessary to reproduce the issue:
    55
    6   Put anything in a dijit ContentPane, cause the pane to be refreshed.  If you have a dockable FloatingPane, a refresh will be triggered when it's minimized/restored.  Also see attached test.html for example to reproduce.
     6 Put anything in a dijit !ContentPane, cause the pane to be refreshed.  If you have a dockable !FloatingPane, a refresh will be triggered when it's minimized/restored.  Also see attached test.html for example to reproduce.
    77
    88An email address of the person filing the bug or a way to get a hold of him/her:  dmiddlecamp@azavea.com
     
    1010Notes:
    1111
    12 Previous functionality allowed the creation of a dijit Content Pane with any nodes / etc inside it.  The Refresh function should be smart enough not to attempt an XHR request if HREF is "".  This causes errors in Firefox 4, and IE 7, because href is "", which is an "invalid argument" in IE7, and causes the content to be replaced with "Loading..." in all browsers.  Could we add a simple
     12Previous functionality allowed the creation of a dijit !ContentPane with any nodes / etc inside it.  The Refresh function should be smart enough not to attempt an XHR request if HREF is "".  This causes errors in Firefox 4, and IE 7, because href is "", which is an "invalid argument" in IE7, and causes the content to be replaced with "Loading..." in all browsers.  Could we add a simple
    1313
    1414if (this._href !== "") { return; }