- From: Matt Falkenhagen <notifications@github.com>
- Date: Tue, 10 Nov 2020 00:31:34 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 November 2020 08:31:46 UTC
Virtual call on November 20, carrying over topics from #1536 ## 20 Nov, 2020 [14:00-16:00 UTC](https://www.timeanddate.com/worldclock/converter.html?iso=20201120T140000&p1=tz_gmt&p2=43&p3=33&p4=248&p5=195&p6=224) Zoom URL TBD ## Meeting notes TBD ## Agenda - **The timing of header setting in fetch** - Sometimes [headers are set pretty late](https://github.com/w3c/ServiceWorker/issues/1542), is this something we should/could change? - **Fix worker timing** - Right now it isn't well described, [can we salvage it](https://github.com/w3c/resource-timing/issues/119#issuecomment-694627668)? - **Determine expected parameter values in Navigation + Resource Timing APIs for responses that have been synthesized using a Service Worker**: https://github.com/w3c/navigation-timing/issues/124 - **Ye old CSS CORS issue** - https://github.com/w3c/ServiceWorker/issues/719 - **The proposal for ServiceWorkerRegistration.id** in #1512. There is a bit of contention on the issue. @wanderview would like to hear wider input to try to resolve things. - **whether cross-origin-isolated value can be platform dependent or not** - https://github.com/w3c/ServiceWorker/pull/1545 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1553
Received on Tuesday, 10 November 2020 08:31:46 UTC