Revert of Remove support for legacy WebKit Notifications (https://codereview.chromium.org/184733002/)

Reason for revert:
Broke interactive_ui_tests and browser_tests, as pointed out by cbiesinger.

http://build.chromium.org/p/chromium.webkit/builders/Linux%20Tests/builds/35005

Original issue's description:
> Remove support for legacy WebKit Notifications
> 
> This patch removes support for the legacy WebKit notifications from Blink,
> per the following Intent to Remove thread:
> 
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/8vqyfHa8_dw
> 
> BUG=348019
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168471

TBR=atwilson@chromium.org,jochen@chromium.org,abarth@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=348019

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168486 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Oilpan: fix build after changes that did not take oilpan into account.

R=haraken@chromium.org, wibling@chromium.org
TBR=betravis@adobe.com, haraken@chromium.org, wibling@chromium.org
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168487 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove CanvasRenderingContext from the web exposed objects

We used have a shared super class called CanvasRenderingContext for
CanvasRenderingContext2D and WebGLRenderingContext. This does not
match the spec and it does not match Firefox or IE.

This removes the web exposed idl file for CanvasRenderingContext. The
method that used to return a CanvasRenderingContext now return a
(CanvasRenderingContext2D or WebGLRenderingContext) instead.

This also allows us to remove the custom bindings that was needed for
CanvasRenderingContext

This is a web exposed visible change. CanvasRenderingContext was
discoverable by walking the prototype chain. It was never exposed as a
named property of Window.

BUG=348012
R=ch.dumez@samsung.com, kbr@chromium.org, tkent@chromium.org

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

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168488 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Include compositing reasons in the "debug" GraphicsLayer tree dump.

It's useful.

R=hartmanng@chromium.org
BUG=None

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168489 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[blink] Avoid null pointer dereference in HitTestResult::isMisspelled()

The method HitTestResult::isMisspelled() assumed that renderer would
always be present in the right-clicked editable item. This is not the case
when right-clicking on an item in an editable combobox created by jQuery
Searchable DropDown Plugin (http://jsearchdropdown.sf.net).

This patch changes HitTestResult::isMisspelled() to check if the renderer
is present. If there's no renderer, then the method returns false (there
shouldn't be spellcheck related items in the context menu).

Manual test 1: Click on the drop-down on http://jsearchdropdown.sf.net and
right-click on any of the items. The page should not crash.

Manual test 2: Run the following script and right-click anywhere on the
page. The page should not crash.

<html>
<head>
<script>
window.onload = function() {
  var element = document.getElementsByTagName('html')[0];
  document.adoptNode(element);
  var newElement = document.createElementNS('http://www.w3.org/2000/svg', 'title');
  document.appendChild(newElement);
  document.execCommand('SelectAll', false)
  document.designMode = 'on';
};
</script>
</head>
</html>

TEST=LayoutTests/editing/spelling/right-click-no-renderer-crash.html
BUG=304165

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168490 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix fast/repaint/block-layout-inline-children-replaced.html

The test was loading an image but didn't wait for the image
to fully load to get all the invalidations generated. The
extra 2 invalidations come from the image (92 x 100)
and its container (402 x 100).

The fix involves allowing our invalidation harness to
run asynchronously. While touching the code, removed
some unneeded window-prefix.

BUG=313447
R=jamesr@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168491 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert of Move all RefPtr's to CSSValue to oilpan transition types, except for the one in CSSCursorImageValue. (https://codereview.chromium.org/184313004/)

Reason for revert:
It seems to break some of our layout tests.

Original issue's description:
> Move all RefPtr's to CSSValue to oilpan transition types, except for the one in CSSCursorImageValue.
> 
> This change gets rid of all but one RefPtr to CSSValue. I have introduced a few persistents core/animation/..., core/css/StylePropertySet, and ElementStyleResources. I plan to attack the one in CSSCursorImageValue subsequently, and then change CSSValue from RefCountedGarbageCollected to GarbageCollectedFinalized.
> 
> R=ager@chromium.org, erik.corry@gmail.com, haraken@chromium.org, oilpan-reviews@chromium.org, tkent@chromium.org, vegorov@chromium.org, zerny@chromium.org
> BUG=341815
> NOTRY=true
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168466

TBR=ager@chromium.org,erik.corry@gmail.com,haraken@chromium.org,oilpan-reviews@chromium.org,tkent@chromium.org,vegorov@chromium.org,zerny@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=341815

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168492 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename Clipboard.idl to DataTransfer.idl to match the spec

http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-datatransfer-interface

The spec uses DataTransfer and both Firefox and IE agrees.

BUG=348580
R=ch.dumez@samsung.com, tkent@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168494 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Move testRunner.startSpeechInput/setValueForUser to internals

Now TestRunner is being moved from CppBoundClass to gin::Wrappable,
where it is not appropriate to use WebElements directly. This CL moves
some functions which treats WebElement* from testRunner to internals.
(To be exact, this CL only copies some functions, but I'll remove those ones
in testRunner later.)

BUG=331301

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168495 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: follow up to r168484, do not add same parent twice into flame chart.

TBR=loislo

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168496 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[import] Use master document's origin to resolve CORS

This follows the spec change on https://www.w3.org/Bugs/Public/show_bug.cgi?id=24905
where the fetch origin is given by the master document, not the referring document.
This matches what CSP in imports is doing: Using master's CSP directive to regulate
all the imports.

In implemntation, it just set ResourceLoaderOptions::m_securityOrigin in
FetchRequest::setCrossOriginAccessControl() because HTMLImportsController
happened to pass the master' origin already.
(That was wrong but wasn't covered by the test.)

This change doesn't affect other FetchRequest client because in other callsite,
m_securityOrigin is same as one that is used when it is absent.

TEST=cors-same-origin.html
BUG=348671
R=abarth@chromium.org, dglazkov@chromium.org

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

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