--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABihn6GnSYYfmsK9LuT1z7fMNkhJXjPCSXQpfpC_enExzhqO9Q%40mail.gmail.com.
No We have browser tests, but we are going to port them to WPT shortly.
Hi,
As part of my work in [1], I noticed that quic-transport was added
in the SchemeRegistry's standard_schemes and secure_schemes [2].
This implies web-exposed changes for which it would be good to
update the spec and add web platform tests. Below are some things
I'm aware.
1. URL using the quic-transport schemes are treated as
"potentially trustworthy" per [3]. I think it makes sense to add
it to step 3 of [3] together with "https" and "wss".
2. Origin with the quic-transport schemes are not treated as
opaque, [4] should probably be updated accordingly.
Additionally,
3. I suspect you want quic-transport to be a "special scheme" so
that its URL parsing is handled consistently with https etc [5].
This can be easily tested e.g. compare the result of new
URL("https:/a/b") vs new URL("notspecial:/a/b")
Note that I already added internal tests for the two first items while working on [1].
Hope that helps,
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1153336
[2]
https://source.chromium.org/chromium/chromium/src/+/master:url/url_util.cc;l=31;drc=09c1e888854f4ca8bf35de6b5e67fead82274ef7
[3]
https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy
[4] https://url.spec.whatwg.org/#concept-url-origin
[5] https://url.spec.whatwg.org/#special-scheme
https://url.spec.whatwg.org/#url-parsing
-- Frédéric Wang
The original QuicTransport origin trial ran (is running) from M84 to M88, and you suggest that the extension is due to a partner just starting their experiment now. The "goals for experimentation" are, however, unchanged. Did you get any developer feedback during that period that would help answer the questions? Do you plan additional changes to the API that a trial extension would help you evaluate? How much of an extension are you asking for to help evaluate the API's shape?
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d9446a5d-a786-3fd1-7068-0d92fccf3473%40igalia.com.
Hi,
Among items 1-3 it seems only the first one had already landed (and without runtime flag).
I'm not sure it's web-exposed, since chrome probably can't load a
page with a quic-transport: scheme anyway, but since you don't
plan to ship the quic-transport: scheme anymore, can you please
remove it from the secure_schemes list:
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABihn6FOBhR%2BXxL6Rt04bgsYo_stfZcHCNxewBx0UK0Zp3QL9w%40mail.gmail.com.
-- Frédéric Wang