Details
-
Type:
Bug
-
Status: Closed
-
Priority:
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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Fix Version/s: 3.2
Resolution: Fixed
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.