Dispatch separate MIDIMessageEvents for multiple messages in the received data buffer.

BUG=163795
TEST=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153213 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename chromium-win* ports to win*

Also renames the ChromiumWinPort class to WinPort.

A later change will update the relevant LayoutTest platform directories
accordingly.

BUG=231188
R=dpranke@chromium.org, ojan@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153214 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Implement PromiseResolver.prototype.resolve.

We are implementing DOM/Promises. 
This CL implements PromiseResolver.prototype.resolve. 
Again, all methods are marked as Custom and there are many boilerplate. we will fix them in a future CL. 
There are no tests. We will add tests in a future. 

R=abarth, haraken
BUG=243345

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153215 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Refactoring: Simplify DocumentWriter by reorganizing its lifetime.

This change simplifies DocumentWriter by

1. Letting its lifetime match to the actual "writing" process:
   It is now created when actual data is arrived to be parsed,
   and is discarded once all the data is loaded.
   Then we no longer neeed DocumentWriter::m_state.

2. Moving most of its Frame dependency to DocumentLoader.
   DocumentWriter::begin() is factored to DocumentLoader::createWriter(), and
   DocumentWriter::replaceDocument is factored to DocumentLoader::replaceDocument()
   and DocumentWriter::appendReplacingData(). DocumentWriter::m_frame is now
   able to be replaced by DocumentWriter::m_documnet. This narrows the dependency surface.
   (Also it makes more sense because it is "document" writer after all.)

3. Making TextResourceDecoderBuilder an immutable object by stripping
   its setters out.

Note that (2) and (3) become possible because of (1).

Key observations here are that

- DocumentWriter had longer lifetime just because it stored mimetype and encoding.
  However, these can be computed on the fly in DocumentLoader when it starts
  actual writing. See ensureWriter() callsites.

- Some of extra states in DocumentWriter was needed because it had to "reset" itself.
  Once its lifetime aligns the single loading/parsing, we no longer need such reset thing.

- The main reason of dependency from DocumentWriter to Frame was DocumentWriter::begin(),
  which did connect the fresh, to-be-built Document and given Frame. This should be part
  of the DocumentWriter creation process and doesn't need to be in DocumentWriter itself.
  This change factors such setup into DocumentLoader::createWriter factory method.

BUG=none
TEST=none
R=abarth@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=153115

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=153125

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153216 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use & instead of | in the value of [CallWith] / [SetterCallWith]

[CallWith=ScriptExecutionContext|ScriptState] meant that both the
ScriptExecutionContext AND the ScriptState would be passed as
arguments to the implementation (not one OR the other).

This patch changes the semantics for those IDL extended attributes
to make it less confusing. Proper usage is now:
[CallWith=ScriptExecutionContext&ScriptState]

R=haraken

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

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