Use the Navigator's frame in navigator.serviceWorker and associated container.

Use the Navigator's frame in navigator.serviceWorker and associated container.

NavigatorServiceWorker's use of CallWith=ExecutionContext meant the
container was configured depending on how it was accessed: for
example, navigator.serviceWorker would associate it with the frame's
execution context; but iframe.contentWindow.navigator.serviceWorker,
window.opener.navigator.serviceWorker,
window.parent.navigator.serviceWorker, etc. would associate it with a
different execution context. This change always retrieves the
execution context from the frame associated with the Navigator object.

Separately, the ServiceWorkerContainerClient was a supplement to the
page, which meant a main frame and an iframe could end up sharing a
ServiceWorkerContainerClient, violating the assumption of a 1:1
relationship between provider and client. This change associates it
with the document.

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

[dominicc (has gone to gerrit), 2014-04-02 05:57:42]

PTAL

[kinuko, 2014-04-02 06:19:54]

Yup this lgtm... was a bit ignorant about page:frames relationship.

[dominicc (has gone to gerrit), 2014-04-02 07:14:57]

The CQ bit was checked by dominicc@chromium.org

[commit-bot: I haz the power, 2014-04-02 07:15:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dominicc@chromium.org/213223005/1

[commit-bot: I haz the power, 2014-04-02 07:46:37]

Change committed as 170641