Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 4.0
-
Fix Version/s: None
-
Component/s: MOBI-Components
-
Labels:None
-
Environment:Tomcat 7, ios 9 device. ace:showcase mobile and icemobile date/time spinner demos
-
Affects:Compatibility/Configuration
Description
Tested date/time spinner demos with ICEfaces 4 trunk showcase and icemobile r46236 using ipad with ios 9.1.
When readOnly = true the date/time fields appear disabled but you can still tap them and access a spinner. Not an issue with ios 7.x, was not able to test with an ios 8 device. See attached screen shot readOnly.jpg.
When readOnly = true the date/time fields appear disabled but you can still tap them and access a spinner. Not an issue with ios 7.x, was not able to test with an ios 8 device. See attached screen shot readOnly.jpg.
Activity
Liana Munroe
created issue -
Liana Munroe
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | readOnly.jpg [ 21997 ] |
Liana Munroe
made changes -
Description |
Tested date/time spinner demos with ICEfaces 4 trunk showcase and icemobile r46236 using ipad with ios 9.1.
When readOnly = true the date/time fields appear disabled but you can still access a spinner. Not an issue with ios 7.x, was not able to test with an ios 8 device. See attached screen shot readOnly.jpg. |
Tested date/time spinner demos with ICEfaces 4 trunk showcase and icemobile r46236 using ipad with ios 9.1.
When readOnly = true the date/time fields appear disabled but you can still tap them and access a spinner. Not an issue with ios 7.x, was not able to test with an ios 8 device. See attached screen shot readOnly.jpg. |
Ken Fyten
made changes -
Affects Version/s | 4.0 [ 11382 ] | |
Affects Version/s | 4.1 [ 11375 ] | |
Affects Version/s | EE-3.3.0.GA_P04 [ 12270 ] |
Ken Fyten
made changes -
Status | Open [ 1 ] | Closed [ 6 ] |
Affects | Compatibility/Configuration [ 10002 ] | |
Resolution | Won't Fix [ 2 ] |
Closing this as won't fix as this issue is an apparent Safari browser bug that was introduced with iOS9. Previous iOS versions do not have this issue.
Accordingly, we will need to wait for a bug fix to be delivered from Apple to resolve, in the meantime this should be considered an known issue.