ICEfaces
  1. ICEfaces
  2. ICE-5329

Provide more granular control of DOM updates

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major 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.

              Issue Links

              blocks

              New Feature - A new feature of the product, which has yet to be developed. ICE-7044 ace:tabSet use DOM difference don't compare don't update element sub-tree (cacheStatically attribute)

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Deryk Sinotte added a comment -

                Initializing assigning to Ted for the discussion/consideration part. Will re-assign if and when we get to the implementation.

                Show
                Deryk Sinotte added a comment - Initializing assigning to Ted for the discussion/consideration part. Will re-assign if and when we get to the implementation.
                Hide
                Permalink
                Ken Fyten added a comment -

                Now that we support partial page rendering (subtree rendering) via f:ajax, is this JIRA complete?

                Show
                Ken Fyten added a comment - Now that we support partial page rendering (subtree rendering) via f:ajax, is this JIRA complete?
                Hide
                Permalink
                Ted Goddard added a comment -

                This JIRA is also intended to support control over whether the diff is applied to a given subtree, so this feature is not yet complete.

                Show
                Ted Goddard added a comment - This JIRA is also intended to support control over whether the diff is applied to a given subtree, so this feature is not yet complete.
                Hide
                Permalink
                Deryk Sinotte added a comment -

                Adding another case to Ted's the DOM optimisation collection.

                Show
                Deryk Sinotte added a comment - Adding another case to Ted's the DOM optimisation collection.
                Hide
                Permalink
                Ted Goddard added a comment -

                It may be necessary to strip the data-ice-diffsuppress="true" attributes from the DOM for XHTML compliance, however, this should simply be tested as most browsers will likely ignore the extra attributes. These marker values are expected to be sparsely used so do not present a performance overhead. Additionally, the presence on the client may be a useful indicator that the page region is under special handling.

                Show
                Ted Goddard added a comment - It may be necessary to strip the data-ice-diffsuppress="true" attributes from the DOM for XHTML compliance, however, this should simply be tested as most browsers will likely ignore the extra attributes. These marker values are expected to be sparsely used so do not present a performance overhead. Additionally, the presence on the client may be a useful indicator that the page region is under special handling.
                Hide
                Permalink
                Ken Fyten added a comment -

                Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.

                Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf

                If the issue persists with the current ICEfaces release, please create a new JIRA for it.

                Show
                Ken Fyten added a comment - Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup. Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf If the issue persists with the current ICEfaces release, please create a new JIRA for it.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Deryk Sinotte
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: