User Login Browser Auto-populate

Marking as duplicate of #165608: Move the label text to the form field value. Please search for existing issues before submitting a new one. You can follow up on that issue instead to track its status. If any information from this issue is missing in the other issue, please make sure you provide it over there.

However, thanks for taking the time to report this issue.

I'm marking this not a duplicate as I read through that other issue and it didn't seem to be related to the field autofill issue that I am also having. I would be more than happy to be proven wrong as long as it results in a solution.

Cheers,
Deciphered.

Example image.

I can confirm this in Google Chrome on Drupal 6.

Here's a complete fix of this issue.

+++ compact_forms.js	19 Sep 2009 17:29:49 -0000
@@ -1,4 +1,4 @@
-// $Id: compact_forms.js,v 1.6 2009/08/06 20:27:22 sun Exp $
+// $Id: compact_forms.js,v 1.4 2009/05/06 23:43:39 sun Exp $

Are you sure you rolled that patch against the latest version in CVS HEAD?

I'm on crack. Are you, too?

Sorry, my bad, copy-paste issue... Here's a correct patch.

Even better patch attached here.

Some notes about the patch:
1. Hiding label instantly cures label flickering (regular .hide() doesn't work in safari).
2. Safari fills it's data without triggering any event, after full page load. So, I see no other way to handle it.

Sorry, misspelled the function name.

Probably the last patch. Firefox doesn't like .hide() by some reason.

+++ compact_forms.js	19 Sep 2009 19:40:17 -0000
@@ -19,7 +19,7 @@
       if ($field.val() != '') {
-        $label.fadeOut(1);
+        $label.css('display', 'none');
       }

The next one who'll touch this code will replace this with .hide().

+++ compact_forms.js	19 Sep 2009 19:40:17 -0000
@@ -50,6 +50,18 @@
+      // Chrome adds his passwords after page load, so we should track it on change.

Exceeds 80 chars.

+++ compact_forms.js	19 Sep 2009 19:40:17 -0000
@@ -62,3 +74,19 @@
 })(jQuery);
+
+// Safari leaves no other way to check auto-filled data.
+if ($.browser.safari) {

This compatibility code for Safari still needs to live within the jQuery closure, because $ is only safely available there.

btw, is $.browser still available in jQuery 1.3 ?

+++ compact_forms.js	19 Sep 2009 19:40:17 -0000
@@ -62,3 +74,19 @@
+  $(window).load(function(){

$(window).load(), to my knowledge, is the same as $.ready(), so we should use that instead.

+++ compact_forms.js	19 Sep 2009 19:40:17 -0000
@@ -62,3 +74,19 @@
+  function checkCompactForms() {

This helper function should have a JSDoc description explaining why it is needed, and the function name should be within the scope of Compact Forms and also could be more precise, either

Drupal.compactForms.fixSafari

or

Drupal.compactForms.onLoad

If you go for the latter, then the JSDoc should be generic, and inline comments should explain the tweak for Safari instead.

This review is powered by Dreditor.

sun, you're killing me :)

OK, heres a new one with your advices applied.

Go ahead! I like your patch! :)

Doesn't appear to resolve the issue I have.

When I have multiple accounts saved for a page, after I enter the user name it auto-populates the password field but doesn't hide the title, resulting in the image at #3

Which browser do you use?

Sorry, thought I mentioned it.
Firefox 3.5.3

This patch did fix a couple bugs with Prefilled forms. But there's still a lingering issue with Autofill.

Video attached. Shows Firefox first then Safari.
http://screenr.com/DiB

I hope this helps. If Firefox remembers your password and you clear the password field then shift+tab out to the username field and tab back in to the password field Firefox re-enters your password. This is not equal to '' and so the label doesn't fade out.

Below we store the default value (the prepopulated value from Firefox) and compare to this...

Around line 14

      var $label = $(this);
      var $field = $('#' + $label.attr('for'));
      if ($field.attr('type') != 'text' && $field.attr('type') != 'password') {
        return;
      }
      var $default_value = $field.val();

      if ($default_value != '') {
        $label.fadeOut(1);
      }

Around line 40

      $field.focus(function () {
        if($(this).val() === $default_value || $(this).val() === '') {
          $label.fadeOut('fast');
        }
      });

      $field.blur(function () {
        if($(this).val() === '') {
          $label.fadeIn('slow');
        }
      });

I wonder however what would happen if you had more than one user's password stored

#13 path work for me!!!

Please test again with this one. Doesn't really change the functionality of the previous patch, but implements the changes a bit differently.

Hi all, thanks for working on this. Still getting the issue with Firefox after applying #21.

The same problem when you use the manager of passwords.

Ctr+Enter in my Opera 9.52

patched #21 against 6.x-1.x-dev and works as expected for me. Would like to see this in an actual release if others can confirm it fixes the issue correctly.

Actually seems to be working for me now! Maybe I patched against the wrong version. Also, never understood why this was marked critical.

Is everyone talking about #21 ?

Yes, I was certainly speaking of your patch #21. Works great. :-)

I can confirm #21 works great with saved passwords (or without) in Firefox 3.6.3 and Chrome 6.0.408.1 dev

Actually, please take a good look at #19 ... it is still an issue.

Ok I have combined #19 and #21 - please review (does no body else get this problem??).

Err... something went wrong with #30 ... another patch attached

For what it's worth (in case more issues come up in the future), I have one site running the Acquia slate theme, which has a compact form functionality built in that handles auto populated fields / incorrect password errors beautifully. Before I came across this thread I was going to try and port the javascript into this or a custom module. Perhaps others would also be interested to see how they accomplished the task.

I can't imagine their approach and code being vastly different to this module. However, a technical review and comparison would be nice to do. Ideally perhaps in a separate issue though, as this one is quite focused.

Not sure what happened here and what the status of this issue/patch is. It seems like some people confirmed that #21 works flawlessly. But there's a revised patch in #31 that accounts for some additional detail mentioned but not fully described in #19, and which has a lot of coding style issues that would need to be fixed.

Would it be a good idea to commit #21 and move the additional changes of #19/#31 into a new issue or follow-up patch?

Patch in 21 works and is an improvement on what's currently in repository. Let's get that in and move forward with a new issue as you suggested.

Thanks for reporting, reviewing, and testing! Committed to all branches.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

Brilliant, I was getting tired of patching this! #19 still applies and I have supplied a patch in #903122: Autofill can cause both password field value and password field label to appear concurrently. - please review.