ICEfaces
  1. ICEfaces
  2. ICE-2027

Safari does not support client UI when there is more than one portlet on the page.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6
          • Fix Version/s: 1.7DR#3, 1.7
          • Component/s: Bridge, Framework
          • Labels:
            None
          • Environment:
            Portal

            Description

            Safari seems to have a problem with client initiated interactions when there is more than one portlet on a page. I could successfully use a single portlet (sync or async) in both Liferay and JBoss. After adding a second portlet to the page, I could no longer interact with either portlet. If it was an async portlet, the clocks would continue to tick (server-push was still working) but any client interaction would fail. Safari's JavaScript console did seem to indicate that there was problem with the bridge (undefined Line 0 and Null value at line 1932).

              Activity

              Hide
              Permalink
              Deryk Sinotte added a comment -

              The bridge and communication with the framework have undergone a number of changes since this was reported. I'm not sure of the exact issue but it appears that Safari does now support client UI interaction when more than one portlet is on the page. Resolving as fixed.

              Show
              Deryk Sinotte added a comment - The bridge and communication with the framework have undergone a number of changes since this was reported. I'm not sure of the exact issue but it appears that Safari does now support client UI interaction when more than one portlet is on the page. Resolving as fixed.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Deryk Sinotte
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: