Our ultimate goal is to compute the value of a content editable on
the browser side.
Until the code that is doing that lands, we need to first separate
the method that retrieves the value of a content editable from the method
that retrieves the values of all other controls.
As it happens, this work also fixes a security bug
that was found in the previous code, because previously it failed to validate that
an <input> element is of type=text, before it attempted to retrieve its value.
Also renames the previous method's name "StringValue" to "GetValueForControl".
This is consistent throughout the whole of the codebase, including the browser.
R=aleventhal@chromium.org, dmazzoni@chromium.org
AX-Relnotes: n/a.
Bug: 1123141, 1187217
Change-Id: I2f30bb1314d5c0bf8d9f0cf5c4a0f1088e9b725a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2767304
Auto-Submit: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#864248}
357ec5e8cf