Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: 4.0
-
Component/s: ACE-Components, Sample Apps
-
Labels:None
-
Environment:HideICEfaces 4.0.Beta release code; IF4 trunk rev.42336
Browsers: all
Server: Tomcat 7.0.42
QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/gMapShowICEfaces 4.0.Beta release code; IF4 trunk rev.42336 Browsers: all Server: Tomcat 7.0.42 QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/gMap
-
Assignee Priority:P2
Description
In the QA test app for ace:gMap, the following tests failed:
1) ace:gMapServices Dynamic Attribute Test (all browsers): a JS error occurs when selecting ``distance`` option in the ``name`` drop-down and enabling ``rendered``:
IE10 & Chrome:
Message: Unable to get property 'charAt' of undefined or null reference
Line: 316
Char: 249
Code: 0
URI: http://localhost:8080/gMap/javax.faces.resource/util/ace-components.js.jsf?ln=icefaces.ace&v=4_0_0_140829
FF31 error:
TypeError: c[1] is undefined
http://localhost:8080/gMap/javax.faces.resource/util/ace-components.js.jsf?ln=icefaces.ace&v=4_0_0_140829
Line 316
Test page: /gMapDynServices.jsf
2) ace:gMapMarker / ace:gMapInfoWindow Test: setting the ``rendered`` checkboxes on or off does not make the markers appear or disappear.
Test page: /gMapMarkerInfoWindow.jsf
1) ace:gMapServices Dynamic Attribute Test (all browsers): a JS error occurs when selecting ``distance`` option in the ``name`` drop-down and enabling ``rendered``:
IE10 & Chrome:
Message: Unable to get property 'charAt' of undefined or null reference
Line: 316
Char: 249
Code: 0
URI: http://localhost:8080/gMap/javax.faces.resource/util/ace-components.js.jsf?ln=icefaces.ace&v=4_0_0_140829
FF31 error:
TypeError: c[1] is undefined
http://localhost:8080/gMap/javax.faces.resource/util/ace-components.js.jsf?ln=icefaces.ace&v=4_0_0_140829
Line 316
Test page: /gMapDynServices.jsf
2) ace:gMapMarker / ace:gMapInfoWindow Test: setting the ``rendered`` checkboxes on or off does not make the markers appear or disappear.
Test page: /gMapMarkerInfoWindow.jsf
Committed fixes to 4.0 trunk at revision 42487.
The error in the first issue was caused because the points weren't supplied in the test app, so a check to see if at least two points were supplied was added in order to prevent the error.
The second issue occurred because the gmap instance needed a explicit call to remove the marker (since the gmap main object stays in memory across requests), so this call was added in an onElementRemove callback.