Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Sparkle
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Create a completely new ACE component to provide a rich, cross-browser selectMenu component.
The high-level initial requirements for selection component are:
- Must support common selection component functionality:
- Select one item from a popup list of options
- Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements.
- Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair.
- Must be fully stylable using CSS, including each selection row item.
- Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list.
- Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item.
- Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item.
- Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior).
- Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary.
- The look and feel of this component must be consistent regardless of the browser it is rendered on.
- Should support extreme lazyInit/proactive cleanup of JavaScript listeners and objects for enhanced scalability (in large dataTables, for example).
The high-level initial requirements for selection component are:
- Must support common selection component functionality:
- Select one item from a popup list of options
- Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements.
- Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair.
- Must be fully stylable using CSS, including each selection row item.
- Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list.
- Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item.
- Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item.
- Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior).
- Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary.
- The look and feel of this component must be consistent regardless of the browser it is rendered on.
- Should support extreme lazyInit/proactive cleanup of JavaScript listeners and objects for enhanced scalability (in large dataTables, for example).
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 2.0 [ 10032 ] | |
| Assignee Priority | P3 | |
| Assignee | Yip Ng [ yip.ng ] |
| Summary | Create a new YUI-based Selection custom component | Create a new Selection component |
| Salesforce Case | [] | |
| Fix Version/s | 2.0.0 [ 10230 ] | |
| Fix Version/s | 2.0-Alpha3 [ 10032 ] | |
| Affects | [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial] | |
| Assignee Priority | P3 | |
| Security | Private [ 10001 ] | |
| Assignee | Yip Ng [ yip.ng ] |
| Component/s | ACE-Components [ 10050 ] | |
| Component/s | Components [ 10012 ] |
| Fix Version/s | 2.1 [ 10241 ] | |
| Fix Version/s | 2.0.0 [ 10230 ] |
| Fix Version/s | 3.1 [ 10312 ] | |
| Fix Version/s | 3.0 [ 10241 ] |
| Summary | Create a new Selection component | New ace:selection component(s) |
| Salesforce Case | [] | |
| Fix Version/s | 3.2 [ 10338 ] | |
| Fix Version/s | 3.1 [ 10312 ] |
| Fix Version/s | 3.3 [ 10370 ] | |
| Fix Version/s | 3.2 [ 10338 ] |
| Assignee | Arturo Zambrano [ artzambrano ] | |
| Assignee Priority | P1 [ 10010 ] |
| Summary | New ace:selection component(s) | New ace:selectMenu component |
| Description |
As part of the new ICEfaces 2.0 Component Suite development project ("Sparkle") we would like to create a completely new custom component that leverages the lower-level YUI utility functions to provide a rich, cross-browser component. The purpose of this exercise is to both create a useful new component for the ICEfaces 2.0 Component Suite (Sparkle), and to further evaluate YUI's suitability for creating all-new custom components (vs. leveraging existing YUI components). The high-level initial requirements for Selection component are: - Must support common selection component functionality: - Select one or more items from a displayed list of options (configurable) - Select one item from a popup list of options - Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements. - Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair. - Must be fully stylable using CSS, including each selection row item. - Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list. - Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item. - Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item. - Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior). - Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary. - The look and feel of this component must be consistent regardless of the browser it is rendered on. - Must leverage YUI utility functions where-ever possible. |
Create a completely new ACE component to provide a rich, cross-browser selectMenu component.
The high-level initial requirements for selection component are: - Must support common selection component functionality: - Select one or more items from a displayed list of options (configurable) - Select one item from a popup list of options - Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements. - Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair. - Must be fully stylable using CSS, including each selection row item. - Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list. - Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item. - Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item. - Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior). - Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary. - The look and feel of this component must be consistent regardless of the browser it is rendered on. - Should support extreme lazyInit/proactive cleanup of JavaScript listeners and objects for enhanced scalability (in large dataTables, for example). |
| Description |
Create a completely new ACE component to provide a rich, cross-browser selectMenu component.
The high-level initial requirements for selection component are: - Must support common selection component functionality: - Select one or more items from a displayed list of options (configurable) - Select one item from a popup list of options - Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements. - Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair. - Must be fully stylable using CSS, including each selection row item. - Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list. - Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item. - Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item. - Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior). - Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary. - The look and feel of this component must be consistent regardless of the browser it is rendered on. - Should support extreme lazyInit/proactive cleanup of JavaScript listeners and objects for enhanced scalability (in large dataTables, for example). |
Create a completely new ACE component to provide a rich, cross-browser selectMenu component.
The high-level initial requirements for selection component are: - Must support common selection component functionality: - Select one item from a popup list of options - Must NOT use the native browser input elements to render the selection list itself. This is to avoid platform/browser specific quirks and differences in behavior with these elements. - Each selection list item may be either a simple String label/value pair, or a facet (with arbitrary complexity, nested components, etc.)/value pair. - Must be fully stylable using CSS, including each selection row item. - Individual selection row items maybe disabled or enabled. When disabled they adopt a disable style appearance and cannot be selected, although they still appear in the list. - Must support keyboard navigation: Arrow keys to move up/down the list, Enter to select the current item. - Must support mouse navigation: highlight list item as hovered over (same as moving up.dwn the list), click to select an item. - Styling must differentiate between a "highlighted/focussed" row and a selected row (similar to current ice:rowSelector behavior). - Ability to size the component either automatically (component will size itself large enough to render it's selection rows), or via CSS width/height. Size attribute may be used on the component if necessary. - The look and feel of this component must be consistent regardless of the browser it is rendered on. - Should support extreme lazyInit/proactive cleanup of JavaScript listeners and objects for enhanced scalability (in large dataTables, for example). |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |