WebKit & WebCore part of the device motion implementation using the platform layer.

Source/WebCore/page/DOMWindow.h

Index: Source/WebCore/page/DOMWindow.h
diff --git a/Source/WebCore/page/DOMWindow.h b/Source/WebCore/page/DOMWindow.h
index 49cb6e617bf53bbeb279b9890ae5067beb5723c2..b316fe67ed7a7a535034ea0605967caed35a7ea1 100644
--- a/Source/WebCore/page/DOMWindow.h
+++ b/Source/WebCore/page/DOMWindow.h
@@ -410,11 +410,11 @@ namespace WebCore {
         void willDetachDocumentFromFrame();
         void willDestroyCachedFrame();
 
+        Page* page();

[Peter Beverloo, 2013/04/09 17:29:53]

I'm almost positive that exposing page() here isn't the way to go.  Is there
another, more common way people store active events for a Page?  Surely Device
Motion isn't the first with this problem?

[timvolodine, 2013/04/10 19:06:12]

ok, made the page() method private again. I switched back to the supplement to a
page approach, with provideDeviceMotionTo(Page*), this is in line with the
comment. Now the controller registers with the pump and is not a singleton
anymore.

+
     private:
         explicit DOMWindow(Document*);
 
-        Page* page();
-
         virtual void frameDestroyed() OVERRIDE;
         virtual void willDetachPage() OVERRIDE;