Bug 57817 (mtorres) - Could not enter weird characters in password input boxes (on MacOS with spanish keyboard)
Summary: Could not enter weird characters in password input boxes (on MacOS with spani...
Status: UNCONFIRMED
Alias: mtorres
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 23:46 PDT by mtorres
Modified: 2011-04-06 10:01 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mtorres 2011-04-04 23:46:27 PDT
NOTE: Probably related to https://bugs.webkit.org/show_bug.cgi?id=32231 (thought I haven't test it on PC Linux)

I've previously reported this at chromium bugtracker (http://code.google.com/p/chromium/issues/detail?id=78048), but they've told me that I should open the ticket here because it's (probably) a webkit issue (the issue is in both, Chrome 10 and Safari 5).

I just copy&paste the report here:

Chrome Version       : 10.0.648
URLs (if applicable) : none
OS version           : MacOS 10.6.7
Behavior in Safari 5.04 (if applicable): 
  The same 
Behavior in Firefox 3.x (if applicable):
  In firefox works like a charm (in both Mac&Win)
Behavior in Chrome for Windows:
  In Chrome Windows works also like a charm (though not tested under Safari for Windows)

What steps will reproduce the problem?
1. Create a web page with input type="password"
<!-- file test.php -->
<?php if (isset($_POST['pwd'])): ?> 
  <?php var_dump($_POST) ?>
<?php else: ?>
<!DOCTYPE html>
<html>
  <head>
    <title>Password test</title>
  </head>
  <body>
    <form action="test.php" method="POST">
      <input type="password" id="pwd" name="pwd" />
      <input type="submit" name="OK" value="Submit" />
    </form>
  </body>
</html>
<?php endif; ?>
2. Try to insert the weird character like ^ in the password field (even `, ´, ¨,  won't work), I just press the character and the the space bar (the SO is expecting another letter to be used, like à or maybe ï, so I type space bar because the password has some of this characters alone).

What is the expected result?
  You'll just expect that the server recieves the characters that you type, but you'll get only the spaces (you can see, using the chrome's developer toolbar, that it's actually sending the typed password wrong!)

What happens instead?
  All the weird characters are repaced by a white space

I've noticed that if I switch the keyboard layout to US it works like a charm (as the system is not expecting another letter to be used when you type those characters so you don't need to type the space bar).

I guess it's a webkit issue, because it also happens in Safari.

I should add that I can type the password on another input box and then cut&paste to the password field. For now this is what I'm doing... (absolutely not the best options if is someone is arround...)
Comment 1 Alexey Proskuryakov 2011-04-05 00:45:24 PDT
It's normal behavior of Mac OS X password input fields that dead keys and non-ASCII input methods are not allowed.
Comment 2 mtorres 2011-04-05 02:07:05 PDT
(In reply to comment #1)
> It's normal behavior of Mac OS X password input fields that dead keys and non-ASCII input methods are not allowed.

But it's working in Firefox (v3.x) but not sure about Opera... Is it normal then?
Comment 3 Alexey Proskuryakov 2011-04-05 11:25:12 PDT
Firefox doesn't use Cocoa password text input control, so it has multiple inconsistencies with other applications. Neither does WebKit, but we strive hard to match Cocoa.

I agree that there is an issue here, but simply allowing dead keys, input methods and non-ASCII-capable input sources would not be a good solution. We haven't come up with a good one yet.
Comment 4 mtorres 2011-04-06 10:01:08 PDT
(In reply to comment #3)
> Firefox doesn't use Cocoa password text input control, so it has multiple inconsistencies with other applications. Neither does WebKit, but we strive hard to match Cocoa.
> 
> I agree that there is an issue here, but simply allowing dead keys, input methods and non-ASCII-capable input sources would not be a good solution. We haven't come up with a good one yet.

Mmm... ok so I can change my password or stay with the cut&paste solution for the moment. Thanks anyway!