Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P2
-
Salesforce Case Reference:
Description
Feature Request: Add support for adding input elements (inputText, commandButton) to the facet section of the ace:comboBox.
Activity
Arran Mccullough
created issue -
Arran Mccullough
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case Reference | 5007000000T6BllAAF |
Ken Fyten
made changes -
Assignee | Arturo Zambrano [ artzambrano ] | |
Fix Version/s | 3.4 [ 10770 ] | |
Assignee Priority | P2 [ 10011 ] |
Ken Fyten
made changes -
Fix Version/s | EE-3.3.0.GA [ 10572 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #35875 | Tue Jun 04 13:34:35 MDT 2013 | art.zambrano | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/combobox/combobox.js
|
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #35883 | Tue Jun 04 14:59:18 MDT 2013 | art.zambrano | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/selectmenu/selectmenu.js
MODIFY /icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/autocompleteentry/autocompleteentry.js |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #35889 | Tue Jun 04 16:09:36 MDT 2013 | art.zambrano | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/selectmenu/selectmenu.js
MODIFY /icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/combobox/combobox.js MODIFY /icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/autocompleteentry/autocompleteentry.js |
Ken Fyten
made changes -
Fix Version/s | 4.0 [ 11382 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Should we trigger the ajax blur event when focusing a focusable element inside the drop-down list?
When a focusable element inside the drop-down list receives focus, the main text field loses it, and if an ajax blur event is registered, we could either fire it or not. If we do, this would cause a request, which in turn could cause a page update and closing the list while the user may be actually intending to interact with the focusable element inside the list. So, I would say no, we shouldn't fire it in this situation, but it's still subject to discussion.