On Fri, Nov 20, 2015 at 3:01 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> > 1) How confident are we that the spec is stable/correct? > The spec is converging to a stable v1, but things are still changing. The core functionality has been stable for a while, though. > 2) How confident are we that our implementation, Chrome's, and the spec > all match? I know we were working on importing some of their tests, so I'm > guessing fairly confident, but just wanted to check. > We imported blink's web-platform-tests. We found some spec issues with them and tried to flow them all back to both spec and google. There are some corner cases where we differ or might differ depending on release schedules. For example, the spec now says that navigations should set a RequestMode of "navigate", but neither chrome or firefox do this. We set "same-origin" as the spec used to say. I believe chrome has patches in flight to change, but we have not started yet. Another compat issue we need to fix is returning the same ServiceWorkerRegistration object repeatedly from certain APIs. This was something that changed a few times in both the spec and chrome. Fixing these minor compat issues is on our todo list for the rest of the 45 cycle leading up to orlando. Also, we have implemented more of the spec in some areas than chrome. For example, I believe chrome's Cache API is still not complete on their release channel. We have a complete Cache API already shipped in FF39. > 3) Have we heard anything from Apple or Microsoft about their plans, or > lack thereof, for Service Workers? > They have been attending face-to-face meetings, but no official implementation announcements as far as I know. The webkit project's 5 year plan includes service workers: http://trac.webkit.org/wiki/FiveYearPlanFall2015 > 4) Are there significant parts of the spec we're not shipping yet? Is > Chrome shipping those parts? Is support for those feature-detectable? > I don't think we are missing anything significant in the service worker spec. Other features building on top of service workers like push, background-sync, etc are in separate specs. Fetch body streams is something that was spec'd recently. Chrome has it partly implemented, but I don't think their shipping implementation is spec compatible. I believe all these APIs are feature detectable. Overall I expect to get reports of compat issues. I think thats inevitable with such a large feature and complex feature. We'll have to hash it out in spec issues, write WPT tests, and ship the fix. I'm not sure how else to realistically move forward, though. I hope that answers your questions. Thanks. Ben _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
