I think that's covered in the Summary of the intent: > This time, we want to ship the core part. The following features are excluded:
- Connection sharing - Stream Prioritization - Statistics - WebTransport over HTTP/2 So, that is intentional. On Wed, Sep 29, 2021 at 11:25 PM Philip Jägenstedt <foo...@chromium.org> wrote: > On Wed, Sep 29, 2021 at 12:32 PM Yutaka Hirano <yhir...@chromium.org> > wrote: > >> Hi Philip, >> >> On Wed, Sep 29, 2021 at 6:29 PM Philip Jägenstedt <foo...@chromium.org> >> wrote: >> >>> Hi Yutaka, >>> >>> This is a big new feature and a lot to go over. When looking at the >>> spec+Blink IDL, I noticed the API didn't require secure contexts: >>> https://bugs.chromium.org/p/chromium/issues/detail?id=1253275 >>> >>> It looks like that's being fixed now, which is great! I'll reply again >>> when I've spent some more time reading here. >>> >> >> Thank you for pointing it out, and sorry for not fixing this earlier. >> > > No worries, it's hard to spot these issues because there's no tooling > around it. > > I have spotted another difference that I'm not sure if it's intentional or > not. The spec has a getStats() method > <https://w3c.github.io/webtransport/#dom-webtransport-getstats> which > isn't implemented and I can't find a bug for it. Is this intentionally left > until later, or should it be in the initial feature set? > > Best regards, > Philip > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABihn6HRV6oMPFU38%2BTVQ%3DAfi86uuVftq4B0serinT7UvJ%2BaMw%40mail.gmail.com.
