Summary: | Secure input can be enabled permanently due to logic error | ||
---|---|---|---|
Product: | WebKit | Reporter: | Greg Scown <greg> |
Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ap |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Mac | ||
OS: | All |
Description
Greg Scown
2012-07-09 17:24:48 PDT
> We have a number of reports that this problem is common with Chrome. It's not common with Safari, but perhaps Safari has a higher-level workaround. This is confusing. The code is only used in Safari, not in Chrome or any other Mac applications. This code is in WebKit2 framework, while Chrome has a completely custom implementation, and regular Mac applications use the original WebKit framework. > However later in the method when EnableSecureEventInput() is called, the internal flag is untouched This observation is not true. The flag is reset in the last line of the function: _data->_inSecureInputState = isInPasswordField; I don't see a bug in this webkit.org code. I'm not quite sure where Chrome code responsible for secure event mode is, I's start with filing a bug at <http://code.google.com/p/chromium/>. |