Prevents sending of 'orgin' in the "Access-Control-Request-Headers" when preflight requests are made.

As per the W3C CORS Spec(http://www.w3.org/TR/cors/#cross-origin-request-with-preflight-0), 
the "Access-Control-Request-Headers" should contain only author request headers. Origin header was
set(by UA) for the actual request before the preflight request was done. 

Avoid setting of Origin header for the actual request in case of preflight. Origin header is anyways
set for the actual request in preflightSuccess(). This makes the behavior same as Mozilla Firefox browser.

R=abarth@chromium.org, kbr@chromium.org, bbudge@chromium.org
BUG=258828

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154346 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Avoid adding placeholder when deleting last text in root

Editing code uses placeholders for all manner of different functions including
holding open content editable blocks. When there's no content in the blocks except
text, these placeholders aren't necessary and is confusing Android's IME path.

Android's IME path should probably just be fixed, but in the meantime, this
creates fewer placeholders, which is definitely an improvement.

The previous version of this patch was rolled out due to crashes, see
https://codereview.chromium.org/14969020. This patch adds a check in
cleanupAfterDeletion to ensure we don't remove ancestors of our destination node,
and yosin@ landed another fix in https://codereview.chromium.org/16053005/.

BUG=222806, 236726

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154347 bbb929c8-8fbe-4397-9dbb-9b2b20218538
r153792 regressed navigating again to the same url.

BUG=259992
TEST=WebFrameTest.NavigateToSame

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154348 bbb929c8-8fbe-4397-9dbb-9b2b20218538
constructTextRun doesn't require a call to bloatedCharacters()

We can construct a TextRun directly from a String without calling
bloatedCharacters now that we support 8 bit TextRuns.

R=eseidel@chromium.org
BUG=254708

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

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154349 bbb929c8-8fbe-4397-9dbb-9b2b20218538
IDBAny need not be scriptwrappable.

V8IDBAnyCustom.cpp will call into toV8() for the appropriate type, which will in turn invoke wrap() for the appropriate type, which will perform the bindings integrity check.  Since IDBAny doesn't have its own wrap() method, there's no place that the check would actually be applied.  The presence of the IDBAny.idl was what triggered the conversion to scriptwrappable in the first place.

This does no harm, but wastes a few bytes of memory.

BUG=260757
R=jsbell@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154350 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Custom Elements: Add annotation-xml to reservedNames.
Add a test to validate all reserved names listed in the spec are handled.

BUG=234509

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154351 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Clear FormAssociatedElement::m_formAttributeTargetObserver on didMoveToNewDocument()

Before this change, didMoveToNewDocument() created new observer instance in didMoveToNewDocument().
This means that the element could have an observer even though it is out-of-document.
This doesn't matter in many cases like appendChild() since the element enters a document eventually.
But document.adoptNode() isn't in the case.

This change just clears the observer in didMoveToNewDocument() instead of refreshing it.
This works because the observer is created in insertedInto() if needed.

TEST=fieldset-adoptnode-crash.html
BUG=260087
R=tkent@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154352 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove StyleResolver::initializeFontStyle as a first step towards cleaning up StyleResolver's font handling

There were two callers to this function.  It turned out that one of them was dead code.

I inlined initializeFontStyle into the remaining caller (defaultStyleForElement()) in preparation
for cleaning up that method's use of StyleResolverState further.

I tried to agressively ASSERT that the !settings codepath in defaultStyleForElement() was dead
code, but it turns out it isn't quite yet.

BUG=237268
R=jchaffraix@chromium.org

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

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