Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: MOBI-Components
-
Labels:None
-
Environment:ICEfaces 4
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Issue Links
- depends on
-
MOBI-882 Refactor flipSwitch into ACE compatible form
- Resolved
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Test Results
1) Is there a reason why the value attribute is an Object type in the docs? Is there another use case besides a regular boolean?
2) The flipswitch value can still be changed and submitted when readonly=true. However, if both readonly and disabled are true then the flipswitch value cannot be changed (which I believe should be the default behaviour for readonly by itself). If disabled=true then the flipswitch can still be changed but the value cannot be submitted (I believe this is expected behaviour).
3) Inherited attributes converter, required, validator (and their messages) should likely be removed from the component since there is no reasonable use case for these.
Remaining issue #4 with nested ace:dataTables has been spun off to
ICE-9895.Marking Resolved.