ICEfaces
  1. ICEfaces
  2. ICE-8658

ace:gMap displays incorrectly in ace:tabSet

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.2.BETA1
    • Fix Version/s: 3.2
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      Any

      Description


      There are some display issues with ace:gMap inside ace:tabSet when switching between tabs.

      Steps to reproduce:
      1. Checkout the test app from this location in the repository
      /svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Manual/gMap
      2. Build and deploy the application.
      3. Navigate to http://localhost:8080/gMap/gMapAceTabSet.jsf
      4. Observe how the map displays correctly.
      4. Click on 'Tab 2'
      5. Click on 'Tab 1'
      6. Notice that the position of the map images within the map frame has changed, and images aren't visible. Also notice that, despite this, the controls are in the correct positions.

      It doesn't seem very likely to be related to css, but rather to some Javascript conflict. It's still not clear whether some of the subcomponents of the gMap have influence in this behaviour.

        Activity

        Migration created issue -
        Hide
        Brennan Mckinney added a comment - - edited

        The issue is being called by the tabset confusing the bounds of the gMap. (You can see if you look at the CSS stylings for the individual map panes.) Calling google.maps.event.trigger(ice.ace.gMap.getGMapWrapper('" + clientId +"').getRealGMap(),'resize'); after the error has occurred will set things right, but the problem seems to happen just after the map is rendered, which means that I can't call if from within the gMap renderer itself.

        Show
        Brennan Mckinney added a comment - - edited The issue is being called by the tabset confusing the bounds of the gMap. (You can see if you look at the CSS stylings for the individual map panes.) Calling google.maps.event.trigger(ice.ace.gMap.getGMapWrapper('" + clientId +"').getRealGMap(),'resize'); after the error has occurred will set things right, but the problem seems to happen just after the map is rendered, which means that I can't call if from within the gMap renderer itself.
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #31504 Tue Oct 16 10:25:35 MDT 2012 brennanm ICE-8658 - Committing minor change to gMap to add a listener when the gMap is inside of a tab set. This should fix the issue with ace:gMap inside ace:tabSet.
        Files Changed
        Commit graph MODIFY /icefaces3/trunk/icefaces/ace/component/src/org/icefaces/ace/component/gmap/GMapRenderer.java
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #31527 Tue Oct 16 17:41:35 MDT 2012 brennanm ICE-8658 - Adding a few lines of code to the listener function to capture and reset the map centre before and after the bounds resizing. This seems to solve the problem completely.
        Files Changed
        Commit graph MODIFY /icefaces3/trunk/icefaces/ace/component/src/org/icefaces/ace/component/gmap/GMapRenderer.java
        Hide
        Brennan Mckinney added a comment - - edited

        Fix Version/s: 3.2
        Resolution: Fixed

        Show
        Brennan Mckinney added a comment - - edited Fix Version/s: 3.2 Resolution: Fixed
        Migration made changes -
        Field Original Value New Value
        Reporter Migration [ remote ] Arturo Zambrano [ artzambrano ]
        Migration made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 3.2 [ 10338 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: