-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create F2F agenda - 7 November 2017 #1206
Comments
@jungkees cheers! I've added the stuff I've been looking at so far to the OP. I'll merge yours into that. I'm sweeping through open issues today. |
We're trying to implement whatwg/fetch#146 and ran into a potentially thorny spec issue in whatwg/fetch#146 (comment). Might be worth talking about in person. |
How do people feel about discussing “meaningless” |
We can discuss it, but standardizing Accept headers is a bit orthogonal to service workers. I recommend raising a fetch spec issue to investigate alignment between browsers on Accept headers. |
While it applies to Ajax situations like |
@tomayac the fetch spec deals with all browser fetching, not just the fetch API. |
I've moved the push API stuff to the morning, so @beverloo can join. |
All spec'd browser networking loading goes through the fetch specification (modulo old specs not updated yet). Not just the |
Thanks both for the clarification. I guess fetch spec issue(s) is the way to go then. |
Planning to start around 09:00 tomorrow. |
Sorry to miss this F2F. Have a really nice and productive session! |
@wanderview points out that we would benefit from better tests for the cache API. |
Action: Add notes about cache sizes + opaque responses. But diversity in mitigation is welcome. |
Action: Built a test that creates a same-origin worker, but in the service worker fetch a response from another origin. According to the spec it should work, and the base url should be the response url. If it fails, @wanderview would be interested in adding that failing to the spec. |
Location
TPAC, Burlingame.
Agenda
Push API
I don't know the details, but I believe the Safari folks have some concerns around the push API, so let's go through that first, timeboxed to an hour.
Changes & bugs
InstallEvent
? It doesn't do anything beyondExendableEvent
now.sw.register()
toLink
headerto confirm
ServiceWorker#postMessage
Interesting feature requests
Clients.matchAll()
should exclude the current environment - OR SHOULD IT? (sorry)Clients.matchAll()
navigation
event - only if there's a 'champion' in the roomThe text was updated successfully, but these errors were encountered: