ICEfaces
  1. ICEfaces
  2. ICE-9025

ICEfaces login page does not propmt to save password in IE and Webkit browsers

          Details

          • Type: Bug Bug
          • Status: Open
          • Priority: Major Major
          • Resolution: Unresolved
          • Affects Version/s: EE-1.8.2.GA_P04, EE-1.8.2.GA_P05, EE-1.8.2.GA_P06
          • Fix Version/s: None
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            IE, Webkit
          • Salesforce Case Reference:
          • Workaround Exists:
            Yes
          • Workaround Description:
            Use a non-ICEfaces login page.

            Description

            When a login page uses ICEfaces the save password notification is not displayed. The reason for this is due to how the browsers are interpreting the form submit. With ICEfaces it is doing an Ajax submit, IE and Chrome does not interpret this as a "real" submit and therefore does not show the dialog.

            With Firefox, instead of relying on the submit type, it simply looks for an input field marked as a password and uses this as its indication to show the dialog.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arran Mccullough added a comment -

              Attached test case that shows issue.

              • Load welcomeICEfaces.jsf for the login page.
              Show
              Arran Mccullough added a comment - Attached test case that shows issue. Load welcomeICEfaces.jsf for the login page.
              Hide
              Permalink
              Ted Goddard added a comment -

              The simplest workaround is to use an HTML or JSP page for just the login page. Was this covered in previous discussions with the customer?

              Show
              Ted Goddard added a comment - The simplest workaround is to use an HTML or JSP page for just the login page. Was this covered in previous discussions with the customer?
              Hide
              Permalink
              Arran Mccullough added a comment -

              Yes it was. I've documented this as a workaround.

              Show
              Arran Mccullough added a comment - Yes it was. I've documented this as a workaround.
              Hide
              Permalink
              Ted Goddard added a comment -

              Do we know why they rejected a non-ICEfaces login page?

              Show
              Ted Goddard added a comment - Do we know why they rejected a non-ICEfaces login page?
              Hide
              Permalink
              Arran Mccullough added a comment -

              No, no response was received after providing my analysis of the issue and the available workarounds.

              Show
              Arran Mccullough added a comment - No, no response was received after providing my analysis of the issue and the available workarounds.
              Hide
              Permalink
              Ted Goddard added a comment -

              It is likely possible to add a feature to support this in ICEfaces 1.8 (similar to prependId="false", perhaps just for ice:inputText, and to disable the ajax submit on the commandButton) but it is necessary to evaluate this against switching to ICEfaces 3.2 or using an HTML/JSP login.

              Show
              Ted Goddard added a comment - It is likely possible to add a feature to support this in ICEfaces 1.8 (similar to prependId="false", perhaps just for ice:inputText, and to disable the ajax submit on the commandButton) but it is necessary to evaluate this against switching to ICEfaces 3.2 or using an HTML/JSP login.
              Hide
              Permalink
              Philip Breau added a comment -

              Arran, was the client saying that simply adding autocomplete='on' to the form tag would solve the problem? Seems to fix the issue for me.

              Show
              Philip Breau added a comment - Arran, was the client saying that simply adding autocomplete='on' to the form tag would solve the problem? Seems to fix the issue for me.
              Hide
              Permalink
              Ted Goddard added a comment -

              autocomplete="on" didn't seem to work for me in Chrome, but maybe it's version-dependent?

              Show
              Ted Goddard added a comment - autocomplete="on" didn't seem to work for me in Chrome, but maybe it's version-dependent?
              Hide
              Permalink
              Philip Breau added a comment - - edited

              On further testing I see that autocomplete="on" on the form is required, but our captured submit on the form in 1.8 prevents Chrome from prompting to save passwords. In 1.8 we also override the h:form renderer, but the h:form doesn't support the HTML5 autocomplete attribute, only the ice:form.

              Show
              Philip Breau added a comment - - edited On further testing I see that autocomplete="on" on the form is required, but our captured submit on the form in 1.8 prevents Chrome from prompting to save passwords. In 1.8 we also override the h:form renderer, but the h:form doesn't support the HTML5 autocomplete attribute, only the ice:form.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Arran Mccullough
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated: