ICEfaces
  1. ICEfaces
  2. ICE-4669

Changing tabs caused "failed to insert element" error in IE

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.1
    • Fix Version/s: 1.8.2-RC1, 1.8.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      IE 6 & 7

      Description

      When changing tabs in a panelTabSet on a page with a command button, the following error is generated:

      [window.7xZl#1] : failed to insert element: <input class="iceCmdBtn headerButton" id="j_id15:cmdHdrHelp" name="j_id15:cmdHdrHelp" onblur="setFocus(&#39;&#39;);" onclick="openHelpWin(&#39;http://java.sun.com&#39;);return false;iceSubmit(form,this,event);return false;" onfocus="setFocus(this.id);" tabindex="21" type="submit" value="Open Help Window">...</input>
      [object Error]
      1. ICE-4669.zip
        8 kB
        yip.ng
      1. ScreenHunter_01.jpg
        96 kB
      2. ScreenHunter_02.jpg
        134 kB
      3. ScreenHunter_03.jpg
        261 kB

        Activity

        yip.ng created issue -
        yip.ng made changes -
        Field Original Value New Value
        Assignee Yip Ng [ yip.ng ]
        yip.ng made changes -
        Salesforce Case []
        Fix Version/s 1.8.2 [ 10190 ]
        yip.ng made changes -
        Attachment ScreenHunter_01.jpg [ 11818 ]
        Attachment ScreenHunter_02.jpg [ 11819 ]
        yip.ng made changes -
        Attachment ICEfacesUpgradeTest_181.war [ 11820 ]
        Hide
        yip.ng added a comment -

        The error occurs when the command button is present with the tab set. If we take out the command button or even replace it with a text input component, there will be no error.

        Show
        yip.ng added a comment - The error occurs when the command button is present with the tab set. If we take out the command button or even replace it with a text input component, there will be no error.
        Hide
        yip.ng added a comment -

        The error was introduced by ICE-4461 at revision 18869.

        Show
        yip.ng added a comment - The error was introduced by ICE-4461 at revision 18869.
        Hide
        yip.ng added a comment -

        Seems IE throws an exception when the font style property is being updated in the DOM.

        Show
        yip.ng added a comment - Seems IE throws an exception when the font style property is being updated in the DOM.
        yip.ng made changes -
        Attachment ICEfacesUpgradeTest_181.war [ 11820 ]
        yip.ng made changes -
        Attachment ScreenHunter_02.jpg [ 11819 ]
        yip.ng made changes -
        Attachment ScreenHunter_02.jpg [ 11823 ]
        Arran Mccullough made changes -
        Salesforce Case [50070000009LN6X]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #19048 Wed Jul 08 16:42:33 MDT 2009 yip.ng ICE-4669
        Changed to avoid exception in IE when updating font style property.
        Files Changed
        Commit graph MODIFY /icefaces/trunk/icefaces/bridge/lib/element.js
        yip.ng made changes -
        Attachment ScreenHunter_03.jpg [ 11827 ]
        yip.ng made changes -
        Attachment ICE-4669.zip [ 11828 ]
        yip.ng made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        yip.ng added a comment -

        When the bridge code tries to update the dom for the style properties of an input element, IE somehow throws an "invalid argument" exception when the property is "font" and the new value is an empty string. (i.e. font property not specified.) All other properties work OK. When the font property is not specified, assigning an empty string is the same as not assigning it all. Therefore we can skip the font property assignment under this condition to avoid the IE exception.

        Show
        yip.ng added a comment - When the bridge code tries to update the dom for the style properties of an input element, IE somehow throws an "invalid argument" exception when the property is "font" and the new value is an empty string. (i.e. font property not specified.) All other properties work OK. When the font property is not specified, assigning an empty string is the same as not assigning it all. Therefore we can skip the font property assignment under this condition to avoid the IE exception.
        Ken Fyten made changes -
        Fix Version/s 1.8.2-RC1 [ 10210 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            yip.ng
            Reporter:
            yip.ng
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: