Alright, time to start adding them service workers to the manifest spec. Proposal: https://github.com/w3c/manifest/issues/161 … //cc @jaffathecake @tobie
-
-
Replying to @marcosc
@marcosc looking at this, I feel like navigator.serviceWorker.register({ src: "/path/to/sw.js", scope: "/*" }); should work.@jaffathecake1 reply 0 retweets 0 likes -
Replying to @tobie2 replies 0 retweets 0 likes
-
Replying to @jaffathecake
@jaffathecake agree with your point, but then I'd like portability with the manifest spec.@marcosc1 reply 0 retweets 0 likes -
Replying to @tobie
@tobie@jaffathecake@marcosc don't stretch a pun too far. I'm fine with just one SW per manifest which simplifies all of this1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate well yes, I agree 1 SW per manifest is what you should optimize for.@jaffathecake@marcosc1 reply 0 retweets 0 likes -
Replying to @tobie
@tobie@jaffathecake@marcosc : then just do: service_worker: "...", service_worker_options: { ... }, ...1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate I thought you might want multiple registrations per app, no?@tobie@jaffathecake1 reply 0 retweets 0 likes -
Replying to @marcosc
@marcosc@tobie@jaffathecake : I don't think we should stress about that. An "app" is the URL scope, and a discontinuous app is trouble3 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate e.g. messaging, pictures and contacts.@marcosc@jaffathecake1 reply 0 retweets 0 likes
@tobie @marcosc @jaffathecake they can integrate via importScripts(), but I take the point
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.