ICEfaces
  1. ICEfaces
  2. ICE-5651

Need to support <f:ajax disabled="true"/>

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha2
          • Fix Version/s: 2.0-Beta1, 2.0.0
          • Component/s: Framework, ICE-Components
          • Labels:
            None
          • Environment:
            ICEfaces 2.0 JSF 2.0
          • Affects:
            Compatibility/Configuration

            Description

            Standard JSF 2, by default, does not enable Ajax functionality in its components. The f:ajax tag is provided to indicate that you want a component (like a button or a whole form) to use Ajax techniques to submit information and update the interface. ICEfaces, by default, enables components to use Ajax but is also designed to work with the f:ajax tag so that certain behaviours can be modified through attributes on the tag. ICEfaces can also be disabled at the page-level so that standard JSF functionality can be configured on pages where ICEfaces and/or Ajax might not be desired.

            What is not currently supported with ICEfaces is disabling Ajax support at a more granular level - ie per component. The f:ajax tag has a 'disabled' attribute, which, if set to true, should disable Ajax features for that component. In these cases, the ICEfaces framework and components should respect when disabled=false and not provide Ajax functionality.

              Issue Links

              blocks

              Task - A task that needs to be done. ICE-5008 Determine the level of framework support for page bookmarking

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                7 older comments
                Hide
                Permalink
                Ted Goddard added a comment -

                Can we reproduce a problem in a certain browser with that line commented out? It will make the f:ajax disabled more complex to implement (we will need to conditionally set f.onsubmit to none in both places).

                Show
                Ted Goddard added a comment - Can we reproduce a problem in a certain browser with that line commented out? It will make the f:ajax disabled more complex to implement (we will need to conditionally set f.onsubmit to none in both places).
                Hide
                Permalink
                Ted Goddard added a comment -

                <f:ajax disabled="true"> has no effect in basic, but is verified working in auction.

                Show
                Ted Goddard added a comment - <f:ajax disabled="true"> has no effect in basic, but is verified working in auction.
                Hide
                Permalink
                Ted Goddard added a comment -

                commandLink is not currently functional: the "onclick" is being handled by the span contained within the commandLink, so is not found in the "disabled" list.

                Show
                Ted Goddard added a comment - commandLink is not currently functional: the "onclick" is being handled by the span contained within the commandLink, so is not found in the "disabled" list.
                Hide
                Permalink
                Joanne Bai added a comment -

                Verified successfully the reload button on the icefaces.jsf page using

                Glimmer revision 21833
                Servers: Tomcat 6.0.26, Glassfish v3 with Mojarra 2.0.2 jars
                Browsers: FF3.6, IE8

                Show
                Joanne Bai added a comment - Verified successfully the reload button on the icefaces.jsf page using Glimmer revision 21833 Servers: Tomcat 6.0.26, Glassfish v3 with Mojarra 2.0.2 jars Browsers: FF3.6, IE8
                Hide
                Permalink
                Ted Goddard added a comment -

                commandLink is now supported.

                Note that <f:ajax disabled="false"> will often have undesirable side effects – this will result in the JSF 2.0 Ajax defaults being applied (such as execute and render "this").

                Optimizations are possible beyond the current implementation: when detecting commandLink, all disabled elements are tested for the existence of hidden fields with that identical name and value. This could be restricted to commandLink elements only.

                Show
                Ted Goddard added a comment - commandLink is now supported. Note that <f:ajax disabled="false"> will often have undesirable side effects – this will result in the JSF 2.0 Ajax defaults being applied (such as execute and render "this"). Optimizations are possible beyond the current implementation: when detecting commandLink, all disabled elements are tested for the existence of hidden fields with that identical name and value. This could be restricted to commandLink elements only.

                  People

                  • Assignee:
                    Ted Goddard
                    Reporter:
                    Deryk Sinotte
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: