Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: EE-4.0.0.GA, 4.1
-
Component/s: MOBI-Components
-
Labels:None
-
Environment:ICEfaces 4 trunk r43111. Tomcat 7. Desktop browsers, ios 7, android 4.4.2
-
Assignee Priority:P2
Description
The rendered and disabled attributes do not work as intended in the mobi:geolocation test app.
1.) When rendered= false, the component is still visible on the page.
2.) When disabled = false the component does not have a ghosted appearance and the button can still be pressed.
But in either case no data is submitted when the attributes = false.
Test app /geolocationDynAttribute.jsf located at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/geolocation
1.) When rendered= false, the component is still visible on the page.
2.) When disabled = false the component does not have a ghosted appearance and the button can still be pressed.
But in either case no data is submitted when the attributes = false.
Test app /geolocationDynAttribute.jsf located at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/geolocation
The mobi:geolocation is properly disabled or not rendered, the component renders just inline javascript code to enable the geolocation causing no visible change in the page. The 'Locate me' button is rendered by a separate h:commandButton.
The fix modifies the h:commmandButton to stop render (or be disabled) when mobi:geolocation is not rendered (or disabled).