GitHub user benkeen opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/546

    Fix for Safari not recognizing autofill on login form

    Safari doesn't trigger change events for form field autofills,
    so the state of the login component doesn't updated, triggering
    the rather irritating "you didn't fill in all the fields" error
    when visually you sure did.
    
    Since existing polyfill options don't work (see ticket), this fix
    explicitly checks for the condition of a mismatch of
    username-password form values and component state. It's a little
    inelegant, but justifiable I think.
    
    Closes COUCHDB-2829

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benkeen/couchdb-fauxton 
safari-login-autofill-bug

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/546.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #546
    
----
commit 71764658aa1c6a195542f8103a6c363f15fb13ed
Author: Ben Keen <[email protected]>
Date:   2015-10-02T17:09:17Z

    Fix for Safari not recognizing autofill on login form
    
    Safari doesn't trigger change events for form field autofills,
    so the state of the login component doesn't updated, triggering
    the rather irritating "you didn't fill in all the fields" error
    when visually you sure did.
    
    Since existing polyfill options don't work (see ticket), this fix
    explicitly checks for the condition of a mismatch of
    username-password form values and component state. It's a little
    inelegant, but justifiable I think.
    
    Closes COUCHDB-2829

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to