MediaStream API: Changing the device enumeration to be async
When we stared to implement this in chrome we discovered that sometimes
device enumeration could take some time and therefore the API needed
to be adjusted. This has been discussed on the W3C email list without
objections but not yet reached the editors draft.
The old name getSourceInfos got changed to getSources as well.

BUG=

Review URL: https://chromiumcodereview.appspot.com/16778002

git-svn-id: svn://svn.chromium.org/blink/trunk@152771 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Bindings: Remove IntegerCache.

It uses ScopedPersistent::get which will be removed. IntegerCache can be removed now,
because ReturnValue takes care of returning integers, so, the cache is not
needed.

The test which used to regress previously when this removal was attempted,
scroll-top.html, no longer regresses.

BUG=236290

Review URL: https://chromiumcodereview.appspot.com/17274007

git-svn-id: svn://svn.chromium.org/blink/trunk@152772 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Reland [Resource Timing] Expose redirect timing information

This change contains redirect timing information for W3C Resource Timing spec, and tests.
To fix previous land which break dbg build bot, this change enable reportLoadTiming for 
XHR preflight, and allow null pointer m_timing in PerformanceResourceTiming for appcache case.

Contributed by pan.deng@intel.com

BUG=252066

Review URL: https://chromiumcodereview.appspot.com/16826017

git-svn-id: svn://svn.chromium.org/blink/trunk@152773 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Implement confirmComposition() for InputMethodContext.

confirmComposition() is expected to commit IME composition text if any.  The behavior is same as when an editor loses focus.

This code assumes that the the node associated with the context is editable.

BUG=238585
TEST=layout test

Review URL: https://chromiumcodereview.appspot.com/16093003

git-svn-id: svn://svn.chromium.org/blink/trunk@152774 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use toHTMLOptionElement as much as possible.

Also, toHTMLOptionElement implmenetations should follow others.
We should use ASSERT_WITH_SECURITY_IMPLICATION even in Release build.

BUG=none
TEST=none; no behavior changes.

Review URL: https://chromiumcodereview.appspot.com/16966014

git-svn-id: svn://svn.chromium.org/blink/trunk@152775 bbb929c8-8fbe-4397-9dbb-9b2b20218538