RESOLVED FIXED112375
[chromium] Add possibleUserNames to WebPasswordFormData
https://bugs.webkit.org/show_bug.cgi?id=112375
Summary [chromium] Add possibleUserNames to WebPasswordFormData
Garrett Casto
Reported 2013-03-14 12:07:41 PDT
Add possibleUserNames to WebPasswordFormData
Attachments
Patch (7.36 KB, patch)
2013-03-14 12:09 PDT, Garrett Casto
no flags
Patch (7.44 KB, patch)
2013-03-15 11:41 PDT, Garrett Casto
no flags
Garrett Casto
Comment 1 2013-03-14 12:09:07 PDT
WebKit Review Bot
Comment 2 2013-03-14 12:12:35 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
WebKit Review Bot
Comment 3 2013-03-14 12:12:50 PDT
Attachment 193168 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit/chromium/ChangeLog', u'Source/WebKit/chromium/public/WebPasswordFormData.h', u'Source/WebKit/chromium/src/WebPasswordFormData.cpp', u'Source/WebKit/chromium/src/WebPasswordFormUtils.cpp', u'Source/WebKit/chromium/src/WebPasswordFormUtils.h']" exit_code: 1 Source/WebKit/chromium/src/WebPasswordFormData.cpp:178: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Total errors found: 1 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
Garrett Casto
Comment 4 2013-03-14 12:28:25 PDT
Additional context at crbug.com/188908
Ilya Sherman
Comment 5 2013-03-14 23:59:52 PDT
Comment on attachment 193168 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=193168&action=review Is there any way to implement this within the Chrome layer, rather than in the WebKit layer? It seems strange to have feature implementation code in the Chromium WebKit glue layer. > Source/WebKit/chromium/src/WebPasswordFormUtils.cpp:-104 > - // Various input types such as text, url, email can be a username field. nit: Did you intentionally remove this comment?
Garrett Casto
Comment 6 2013-03-15 11:38:28 PDT
(In reply to comment #5) > (From update of attachment 193168 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=193168&action=review > > Is there any way to implement this within the Chrome layer, rather than in the WebKit layer? It seems strange to have feature implementation code in the Chromium WebKit glue layer. > It looks like this could be implemented in content if we wanted to do that. I made this change because at the moment all parsing for content::PasswordForm happens here and I thought that it made sense to keep it together. Though now that you mention it, I'm not sure if there is a good reason for this code to live in WebKit or if it's just leftover from a time when the Chromium WebKit API wasn't expansive enough. WebKit reviewers, do you have any thoughts on either if this change should go here or in Chromium, or if this code in general (WebPasswordFormData and WebPasswordFormUtils) should stay in WebKit long term. > > Source/WebKit/chromium/src/WebPasswordFormUtils.cpp:-104 > > - // Various input types such as text, url, email can be a username field. > > nit: Did you intentionally remove this comment? No, good catch.
Garrett Casto
Comment 7 2013-03-15 11:41:29 PDT
WebKit Review Bot
Comment 8 2013-03-15 11:49:11 PDT
Attachment 193342 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit/chromium/ChangeLog', u'Source/WebKit/chromium/public/WebPasswordFormData.h', u'Source/WebKit/chromium/src/WebPasswordFormData.cpp', u'Source/WebKit/chromium/src/WebPasswordFormUtils.cpp', u'Source/WebKit/chromium/src/WebPasswordFormUtils.h']" exit_code: 1 Source/WebKit/chromium/src/WebPasswordFormData.cpp:178: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Total errors found: 1 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
Adam Barth
Comment 9 2013-03-19 20:48:37 PDT
Comment on attachment 193342 [details] Patch API change LGTM
Garrett Casto
Comment 10 2013-03-20 16:54:58 PDT
Can I get an r+ and cq+?
Adam Barth
Comment 11 2013-03-20 21:19:20 PDT
(In reply to comment #10) > Can I get an r+ and cq+? Who do you have in mind to review your change?
Garrett Casto
Comment 12 2013-03-21 12:29:18 PDT
Ah, apologies. isherman@ was going to review the content of this change, but the LGTM that he gave me was out of band. Ilya, do you mind?
Ilya Sherman
Comment 13 2013-03-21 14:07:33 PDT
Right, I'm not a reviewer, but the content of this change LGTM if we're cool with keeping this code in WebKit.
WebKit Review Bot
Comment 14 2013-03-21 14:32:42 PDT
Comment on attachment 193342 [details] Patch Clearing flags on attachment: 193342 Committed r146521: <http://trac.webkit.org/changeset/146521>
WebKit Review Bot
Comment 15 2013-03-21 14:32:46 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.