Does Chrome allow ServiceWorkers inside <iframe sandbox>? o_O https://code.google.com/p/chromium/issues/detail?id=439730#c9 … /cc @sleevi_
-
-
Replying to @bascule1 reply 0 retweets 0 likes
-
Replying to @slightlylate
@slightlylate@bascule Doesn't seem to quite answer the question (in comment #8) re: iframe sandboxes. #9 answers a different question.2 replies 0 retweets 0 likes -
Replying to @sleevi_
@slightlylate@bascule I mean, Tony's not the only one confused - https://github.com/slightlyoff/ServiceWorker/issues/648 …1 reply 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_@slightlylate having an <iframe sandbox> that doesn’t allow-scripts register a ServiceWorker seems slightly insane to me2 replies 0 retweets 1 like -
Replying to @bascule
@bascule@sleevi_@slightlylate A !allow-scripts page wouldn't be able to register a SW since doing that requires script, right?2 replies 0 retweets 1 like -
Replying to @jyasskin
@jyasskin@sleevi_@slightlylate and with allow-scripts it could still install a ServiceWorker on the sandbox’s (unique) origin?1 reply 0 retweets 0 likes -
Replying to @bascule2 replies 0 retweets 0 likes
-
Replying to @slightlylate
@slightlylate@bascule@sleevi_ http://lists.w3.org/Archives/Public/public-webappsec/2014Jul/0109.html …, says a !same-origin iframe would fail because the SW script must be same-origin.4 replies 0 retweets 2 likes -
Replying to @jyasskin1 reply 0 retweets 1 like
@slightlylate @jyasskin @sleevi_ well then, seems ok ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.