ICEfaces
  1. ICEfaces
  2. ICE-5123

JS error in IE when using Autocomplete in component-showcase

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 2.0-Alpha1
          • Fix Version/s: 2.0-Alpha2, 2.0.0
          • Component/s: Bridge
          • Labels:
            None
          • Environment:
            browser

            Description

            Error occurirng in IE when using Autocomplete :

            Message: 'Ice.ElementModel.Element' is null or not an object
            Line: 8906
            Char: 13
            Code: 0
            URI: http://localhost:8080/component-showcase/javax.faces.resource/ice-extras.js.jsf

              Issue Links

              blocks

              New Feature - A new feature of the product, which has yet to be developed. ICE-4458 create component-showcase sample for compat version of ICEfaces-2

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #19655 Mon Nov 09 15:45:24 MST 2009 mircea.toma ICE-5123 Avoid using Ice.ElementModel object since its definition is not present in Glimmer. Apply alternative solution for referencing a blank page as the src of the iframe.
                Files Changed
                Commit graph MODIFY /icefaces/scratchpads/glimmer/compat/core/src/main/resources/META-INF/resources/ice-extras.js
                Mircea Toma created issue -
                Mircea Toma made changes -
                Field Original Value New Value
                Assignee Mircea Toma [ mircea.toma ]
                Mircea Toma made changes -
                Link This issue blocks ICE-4458 [ ICE-4458 ]
                Hide
                Permalink
                Mircea Toma added a comment -

                Avoided to use Ice.ElementModel object since its definition is not present in Glimmer anymore (used to be in 1.8.*). The alternative solution was to use a pseudo URL for the 'src' of the iframe. The 'javascript:...' pseudo URL allows you to define the content of the page right inside in the URL avoiding thus the need for having a reference to a blank page.
                Anyway, the previous solution was way to ugly since it was drilling down inside bridge's code to lookup a variable that contained a URL. This URL was then used to calculate the context path which in turn allowed for calculating an absolute path to a blank page.....

                Show
                Mircea Toma added a comment - Avoided to use Ice.ElementModel object since its definition is not present in Glimmer anymore (used to be in 1.8.*). The alternative solution was to use a pseudo URL for the 'src' of the iframe. The 'javascript:...' pseudo URL allows you to define the content of the page right inside in the URL avoiding thus the need for having a reference to a blank page. Anyway, the previous solution was way to ugly since it was drilling down inside bridge's code to lookup a variable that contained a URL. This URL was then used to calculate the context path which in turn allowed for calculating an absolute path to a blank page.....
                Mircea Toma made changes -
                Status Open [ 1 ] Resolved [ 5 ]
                Fix Version/s 2.0-Alpha2 [ 10214 ]
                Resolution Fixed [ 1 ]
                Hide
                Permalink
                Mircea Toma added a comment -

                Solution courtesy of http://weblogs.asp.net/bleroy/archive/2005/08/09/how-to-put-a-div-over-a-select-in-ie.aspx .

                Show
                Mircea Toma added a comment - Solution courtesy of http://weblogs.asp.net/bleroy/archive/2005/08/09/how-to-put-a-div-over-a-select-in-ie.aspx .
                Hide
                Permalink
                Ken Fyten added a comment -

                Seems very likely that using "JavaScript:" in the src tag will cause IE browsers to present security warning dialogs when rendering via HTTPS/SSL. For example, http://jira.icefaces.org/browse/ICE-4179.

                Show
                Ken Fyten added a comment - Seems very likely that using "JavaScript:" in the src tag will cause IE browsers to present security warning dialogs when rendering via HTTPS/SSL. For example, http://jira.icefaces.org/browse/ICE-4179 .
                Ken Fyten made changes -
                Resolution Fixed [ 1 ]
                Status Resolved [ 5 ] Reopened [ 4 ]
                Hide
                Permalink
                Mircea Toma added a comment -

                I checked and doubled checked if the pseudo-URL of the form javascript:'<html></html>'; causes any problems. I can confirm that the pseudo-URL solution is working just fine without causing "This page contains both secure and nonsecure items" popup to appear.

                Component-showcase in "compat" does get the "This page contains both secure and nonsecure items" popup but changing the iframes to point to a real URL (blank page) or pseudo URL won't make a difference. But by just re-organizing the JSF markup the alert will go away. This seems to point to a problem reported by other people on the web: http://support.microsoft.com/kb/925014 . This problem can be fixed at application level by changing the used CSS.

                Show
                Mircea Toma added a comment - I checked and doubled checked if the pseudo-URL of the form javascript:'<html></html>'; causes any problems. I can confirm that the pseudo-URL solution is working just fine without causing "This page contains both secure and nonsecure items" popup to appear. Component-showcase in "compat" does get the "This page contains both secure and nonsecure items" popup but changing the iframes to point to a real URL (blank page) or pseudo URL won't make a difference. But by just re-organizing the JSF markup the alert will go away. This seems to point to a problem reported by other people on the web: http://support.microsoft.com/kb/925014 . This problem can be fixed at application level by changing the used CSS.
                Mircea Toma made changes -
                Status Reopened [ 4 ] Resolved [ 5 ]
                Resolution Won't Fix [ 2 ]
                Ken Fyten made changes -
                Fix Version/s 2.0.0 [ 10230 ]
                Ken Fyten made changes -
                Status Resolved [ 5 ] Closed [ 6 ]

                  People

                  • Assignee:
                    Mircea Toma
                    Reporter:
                    Mircea Toma
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: