Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6.1
-
Fix Version/s: 2.1-Beta, 3.0, EE-1.8.2.GA_P04
-
Component/s: ICE-Components
-
Labels:None
-
Environment:all
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
Description
The maxlength attribute of ice:selectInputText does not work but is included as an attribute in the tld. http://www.icesoft.com/developer_guides/icefaces/tld/ice/selectInputText.html
Issue Links
- duplicates
-
ICE-2338 <ice:selectInputText>, various attributes are being passed through to the wrong element
- Closed
Activity
Tyler Johnson
created issue -
Chris Johnson
made changes -
Arran Mccullough
made changes -
Salesforce Case | [50070000008Jidz] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #25107 | Tue Jul 26 14:47:40 MDT 2011 | yip.ng | |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/component/src/com/icesoft/faces/component/selectinputtext/SelectInputTextRenderer.java
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #25108 | Tue Jul 26 14:48:31 MDT 2011 | yip.ng | |
Files Changed | ||||
MODIFY
/icefaces2/trunk/icefaces/compat/components/src/main/java/com/icesoft/faces/component/selectinputtext/SelectInputTextRenderer.java
|
Mark Collette
made changes -
Assignee | yip.ng [ yip.ng ] |
Mark Collette
made changes -
Assignee Priority | P1 |
Mark Collette
made changes -
Fix Version/s | 2.1 [ 10241 ] | |
Fix Version/s | EE-1.8.2.GA_P04 [ 10280 ] |
yip.ng
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
yip.ng
made changes -
Assignee | yip.ng [ yip.ng ] | Arran Mccullough [ arran.mccullough ] |
Arran Mccullough
made changes -
Salesforce Case | [50070000008Jidz] | [50070000008Jidz, 5007000000HzZmN] |
Ken Fyten
made changes -
Fix Version/s | 2.1-Beta [ 10291 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
ICE-2338seems to be related to, or perhaps a duplicate of this issue. That issue was closed unfixed, but no work-around appears to have been given.It seems there is still no solution to this issue, and remains an outstanding issue in the latest release (1.7.0)