summaryrefslogtreecommitdiffstats
path: root/content/shell/webkit_test_controller.cc
diff options
context:
space:
mode:
authorrmsousa@chromium.org <rmsousa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-03-24 05:26:03 +0000
committerrmsousa@chromium.org <rmsousa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-03-24 05:26:03 +0000
commit05e489c0f0d2a12c70f7dc053eb28dc6546503e8 (patch)
tree265f76cbf0d66cda9fefe782c8fd7dfee7d6cbbb /content/shell/webkit_test_controller.cc
parentcad2491b94d4617e50bac26c9ae8f5cef02311c1 (diff)
downloadchromium_src-05e489c0f0d2a12c70f7dc053eb28dc6546503e8.zip
chromium_src-05e489c0f0d2a12c70f7dc053eb28dc6546503e8.tar.gz
chromium_src-05e489c0f0d2a12c70f7dc053eb28dc6546503e8.tar.bz2
Webapp changes to support asking for a PIN
This implements a fetchPin interface, that can be called when the plugin layer needs a PIN, and calls onPinFetched with the PIN once it's obtained from the user. With old plugins, that don't support the useAsyncPinDialog API, this runs the dialog immediately before connecting, and then connects using the existing APIs. Finally, for It2Me nothing is changed, the support code is used as the passphrase as usual. BUG=115899 Review URL: https://chromiumcodereview.appspot.com/12867004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@190207 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/shell/webkit_test_controller.cc')
0 files changed, 0 insertions, 0 deletions