Moved ParseFileSystemSchemeURL from file_system_url to file_system_util.

This makes it available to renderer code (previously it was only
available to the browser), which will be required to receive file system
objects from Pepper plugins. The static method was not really related to
the FileSystemURL class, it's just used by FileSystemURL's
implementation (among other uses), so it did not belong there anyway.

BUG=345158

Review URL: https://codereview.chromium.org/176263003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253759 0039d316-1c4b-4281-b951-d872f2087c98
Search provider extension names should be strings

R=jochen@chromium.org

BUG=346164

Review URL: https://codereview.chromium.org/179503002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253760 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 253760
Followup to modifications to ReadFileToString function

This CL cleans up the changes done as part of https://codereview.chromium.org/157593005/

A minor change is done to the unit test along with some changes to the API documentation in the header.

BUG=339417

Review URL: https://codereview.chromium.org/177073018

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253761 0039d316-1c4b-4281-b951-d872f2087c98
Make sure we don't call DisableKeyPressMonitoring without calling EnableKeyPressMonitoring first.

If we fail to open an audio device, AudioInputDeviceController can call DisableKeyPressMonitoring() and bring the monitoring reference count to below 0.  The state of the AudioInputDeviceController instance will be |kEmpty| in this case but the DoClose() code only checks for kClosed.

The class has 2 states that aren't really necessary.  kError is never used, so I'm just removing it.  kEmpty is only used from construction until successful initialization.  It is this state (kEmpty) that is never checked for and can cause us to call DisableKeyPressMonitoring inside DoClose without having first called EnableKeyPressMonitoring.

Since I'm cleaning up the states, I'm also fixing them as far as Chromium style goes.

BUG=347129
TEST=I ran into this while opening apprtc.appspot.com with a debug build of Chrome on Windows where my 'default communication device' was not the same as the 'default device'.  These two different devices furthermore did not have the same sample rates, which caused opening the communication device with the incorrect parameters to fail.  That's when I hit a DCHECK inside DisableKeyPressMonitoring where key_press_counter_references_ was being set to -1.

Review URL: https://codereview.chromium.org/181553003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253762 0039d316-1c4b-4281-b951-d872f2087c98
Revert "Adds support for capturing a sub rect of the compositing surface."

This reverts https://codereview.chromium.org/173023005. It is an Android only
change breaking downstream Android bots.

TBR=clholgat@chromium.org,sievers@chromium.org,tedchoc@chromium.org
BUG=

Review URL: https://codereview.chromium.org/183063002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253763 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 253763