Opened 17 years ago
Closed 17 years ago
#1474 closed Bug (fixed)
null errors reloading the page in IE
Reported by: | Alfonso Martínez de Lizarrondo | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | FCKeditor 2.5 |
Component: | General | Version: | FCKeditor 2.5 Beta |
Keywords: | Confirmed IE | Cc: |
Description
Add a smiley to the content in IE 6 and now try to reload the page, a list of errors saying that something is null will show.
This patch (it's missing the reference to this bug number as it still doesn't exists) should take care of them, but maybe there's something else that can be done:
-
classes/fckspecialcombo.js
192 192 { 193 193 this.Enabled = isEnabled ; 194 194 195 this._OuterTable.className = isEnabled ? '' : 'SC_FieldDisabled' ; 195 // In IE it can happen when the page is reloaded that _OuterTable is null, so check its existence 196 if ( this._OuterTable ) 197 this._OuterTable.className = isEnabled ? '' : 'SC_FieldDisabled' ; 196 198 } 197 199 198 200 FCKSpecialCombo.prototype.Create = function( targetElement ) -
classes/fcktoolbarbuttonui.js
127 127 128 128 var e = this.MainElement ; 129 129 130 // In IE it can happen when the page is reloaded that MainElement is null, so exit here 131 if ( !e ) 132 return ; 133 130 134 switch ( parseInt( newState, 10 ) ) 131 135 { 132 136 case FCK_TRISTATE_OFF : -
internals/fckdomtools.js
380 380 381 381 EnforcePaddingNode : function( doc, tagName ) 382 382 { 383 // In IE it can happen when the page is reloaded that doc or doc.body is null, so exit here 384 if ( !doc || !doc.body ) 385 return ; 386 383 387 this.CheckAndRemovePaddingNode( doc, tagName, true ) ; 384 388 if ( doc.body.lastChild && ( doc.body.lastChild.nodeType != 1 385 389 || doc.body.lastChild.tagName.toLowerCase() == tagName.toLowerCase() ) )
Change History (1)
comment:1 Changed 17 years ago by
Keywords: | Confirmed added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I've merged the proposed fix to trunk in [1047].
Interestingly, the bug seems to be related to the popup dialogs. While I can confirm the bug definitely occurs with the 2.5.x branch code, it didn't occur in my local trunk code which uses floating iframes for dialogs (I haven't committed the floating dialog code to trunk yet as I still need to add in the graphics stuff).