summaryrefslogtreecommitdiffstats
path: root/Source/WebKit/android/WebCoreSupport/autofill
Commit message (Collapse)AuthorAgeFilesLines
* Audit misuse of PassRefPtrRussell Brenner2011-11-161-1/+1
| | | | | | | | Reviewed Android code for misuse of PassRefPtr in place of RefPtr. Also reviewed for PassOwnPtr and found no apparent misuse. Bug: 5631569 Change-Id: Ib22b340875b1d875091af47cef6510d9c63e351b
* Fix crash in Autofill.Ben Murdoch2011-11-031-7/+9
| | | | | | | | Fix a crash in autofill that can be caused by toggling the setting on and off. Bug: 5452927 Change-Id: I80ba0b823fd16cb4e2df3359be95f3d063a9b091
* Part of fix for bug 5152544 Reduce the number of warningKristian Monsen2011-08-111-1/+1
| | | | Change-Id: I06a7975d6b08f01731b8bd1761141e3aba942393
* Preparation for fixing bug 5065047: build libchromium as a shared libKristian Monsen2011-07-283-215/+0
| | | | | | | Use FormField from chromium, it is already populated it FormManagerAndroid, so there is no need for the Android implementation anymore. Change-Id: I1ee0fbf6895bd64b2fd1d9a6fbd2f0a93e578831
* Merge Chromium at r12.0.742.93: Update Autofill files in WebKit.Ben Murdoch2011-07-125-175/+208
| | | | | | | | | | | | | Apply diffs to the forked copies of Chromium files we keep in external/webkit. See: http://src.chromium.org/viewvc/chrome/branches/742/src/chrome/renderer/autofill/form_manager.cc?r1=67599&r2=82248 http://src.chromium.org/viewvc/chrome/branches/742/src/chrome/renderer/autofill/form_manager.h?r1=67599&r2=82248 http://src.chromium.org/viewvc/chrome/branches/742/src/webkit/glue/form_field.cc?r1=67599&r2=82248 http://src.chromium.org/viewvc/chrome/branches/742/src/webkit/glue/form_field.h?r1=67599&r2=82248 Change-Id: If62167848d86293cb833c593afd2c0c958bafbef
* Merge Chromium at r12.0.742.93: Direct access in FormFieldKristian Monsen2011-07-074-70/+58
| | | | | | | | FormField changed to a struct with public members instead of a class with setters and getters. CL: http://codereview.chromium.org/6625087 Change-Id: I02f589b671147c1ff09661b032c979c85e15a264
* Merge Chromium at r12.0.742.93: Autofill fixesKristian Monsen2011-07-072-17/+17
| | | | | | | | | | AutoFillProfile -> AutofillProfile renaming: http://codereview.chromium.org/6658030 Moved from AutofillType to AutofillFieldType, upstream CL: http://src.chromium.org/viewvc/chrome/branches/742/src/chrome/browser/autofill/autofill_profile.h?r1=77630&r2=78518&pathrev=88489 Change-Id: Ie54a0054221d28b20622f94dd882975c73a5aec1
* Merge Chromium at r11.0.696.0: Just AutoFill => Autofill renamingKristian Monsen2011-06-294-75/+75
| | | | Change-Id: Iefb91f0b784c26b503125017ae3582a28e7d530d
* Rmove unnecessary passing of unused parameterBen Murdoch2011-06-161-1/+1
| | | | | | | Requires a change in external/chromium, see If349cd2ffd56b9f539d4ebdb8944964fc57289e5 Change-Id: I88d7c291ee1ffd1b1c413ffaf59acf5e4ae57c78
* Merge changes I637b26fb,Icf028ea9Kristian Monsen2011-06-141-3/+3
|\ | | | | | | | | | | * changes: Merge Chromium at r11.0.672.0: Fix autofill Merge Chromium at r11.0.672.0: Compile fixes
| * Merge Chromium at r11.0.672.0: Fix autofillKristian Monsen2011-06-081-3/+3
| | | | | | | | | | | | | | | | | | | | Major refactoring in CL: http://codereview.chromium.org/5958021 Created wrapper function to call in chromium CL: https://android-git.corp.google.com/g/#change,113980 Change-Id: I637b26fb2e3ccb544adfc818b94047ef5a2c5aad
* | Fix some include guards in Android filesSteve Block2011-06-081-2/+2
|/ | | | | | | | | This will become relevant after we merge beyond http://trac.webkit.org/changeset/81977 (and its follow-up build fixes r81982, r81988, r81990, r82018) which relies on all platforms' instances of FontPlatformData.h using the correct include guard. Change-Id: I58ec4c8ee23698c41d86794333d603b95f303764
* Merge WebKit at r76408: Update Uses of Noncopyable/FastAllocBaseBen Murdoch2011-05-231-1/+2
| | | | | | | | | | | | | | | | Upstream now uses macros rather than inheritance for classes declard Noncopyable or Fast Allocated. Note that in the case of PluginTimer and ClipboardAndroid we now need to explicitly declare them fast allocated. This is because previously they got the fast allocated methods through a common superclass (FastAllocBase) but now both parents provide implementations, so there is an ambiguity the compiler cannot resolve. See http://trac.webkit.org/changeset/76248 Change-Id: I186e3fd36bde2074d34f453983d48e8fc223f420
* Merge WebKit at r75993: Move WebKit/android files to SourceBen Murdoch2011-05-1611-0/+1966
Change-Id: Ifa871f8320bdb3a09fe189fffecc23f702c394b9
generated by cgit v1.1 at 2025-09-14 08:07:23 +0000