[DONT COMMIT] PaintWorklet: Move paintWorklet from 'window' to 'CSS'

third_party/WebKit/Source/modules/csspaint/CSSPaintWorklet.cpp

+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "modules/csspaint/CSSPaintWorklet.h"
+
+#include "core/css/DOMWindowCSS.h"
+#include "core/dom/Document.h"
+#include "core/frame/LocalDOMWindow.h"
+#include "core/frame/LocalFrame.h"
+#include "modules/csspaint/PaintWorklet.h"
+
+namespace blink {
+
+// static
+Worklet* CSSPaintWorklet::paintWorklet(ScriptState* script_state) {
+  return paintWorklet(*ToDocument(ExecutionContext::From(script_state)));
+}
+
+// static
+PaintWorklet* CSSPaintWorklet::paintWorklet(Document& document) {
+  DLOG(ERROR) << document.Url().GetString();

[nhiroki, 2017/06/13 08:56:58]

yukishiino@: I have a question.

In LayoutTests/http/tests/worklet/chromium/import-on-detached-iframe.html, this
log prints "import-on-detached-iframe.html" that is the main frame's URL. This
means "frame.contentWindow.CSS.paintWorklet" passes the main frame's ScriptState
to CSSPaintWorklet::paintWorklet(). Is this right behavior? I expect that
attribute access passes the iframe's ScriptState and this log prints the
iframe's URL "resources/blank.html".

[nhiroki, 2017/06/13 09:41:56]

Sample log:

[1:1:0613/021034.138374:3361121614:ERROR:CSSPaintWorklet.cpp(22)]
"http://127.0.0.1:8000/worklet/chromium/import-on-detached-iframe.html"

https://storage.googleapis.com/chromium-layout-test-archives/linux_chromium_r...

[nhiroki, 2017/06/13 10:13:38]

According to yukishiino@, this could be a bug in V8...

See https://bugs.chromium.org/p/v8/issues/detail?id=6156

+  return PaintWorklet::From(*document.ExecutingWindow());
+}
+
+}  // namespace blink