Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 2.0-Alpha2
-
Fix Version/s: None
-
Component/s: Bridge, Framework, ICE-Components
-
Labels:None
-
Environment:ICEfaces 2
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
One of the main benefits of ICEfaces has always been the transparency with which DOM updates are applied. The developer generally doesn't have to provide anything in the page markup or the back end to have the client side updated properly. However, as we move towards better integration with 3rd party components, this type of page-scoped updating can sometimes cause problems as other components/scripts/etc on the page may not operate properly if updated by ICEfaces. It's also possible that turning off updates for a page region could provide optimized performance.
This JIRA is the starting point for a discussion about the usefulness of such a feature and how it might be implemented. For example, one option would be to provide a container component that support attributes for controlling if and how a containing region was updated.
This JIRA is the starting point for a discussion about the usefulness of such a feature and how it might be implemented. For example, one option would be to provide a container component that support attributes for controlling if and how a containing region was updated.
Issue Links
- blocks
-
ICE-7044
ace:tabSet use DOM difference don't compare don't update element sub-tree (cacheStatically attribute)
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion