Shunya Shishido

@annevk Thank you for your help, I think the venue issue of URLPattern was resolved. Do you think this status can be updated as well?

> Wouldn't this return a response without any filtering getting applied? I guess the idea is that these are already filtered responses? Can that be asserted? @annevk Sorry to be...

@SanderElias Actually the spec was already merged. chromium is going to update the flag, too fyi ([blink-dev thread](https://groups.google.com/a/chromium.org/g/blink-dev/c/yW453lPWjpc)). Here is the updated tests. https://github.com/web-platform-tests/wpt/pull/43014

Thank you for raising this. > The shorthand form can't set the options (i.e. ignoreCase) In https://github.com/WICG/compression-dictionary-transport/pull/51#issuecomment-1714280658, the new option to `URLPatternOptions` is proposed. So this limitation may be more...

I feel it's better to expose this API to the [URLPattern](https://urlpattern.spec.whatwg.org/#urlpattern) interface, rather than making it mutable with adding `toString()` in [URLPatternResult](https://urlpattern.spec.whatwg.org/#dictdef-urlpatternresult), which is currently defined as dictionary and doesn't...

We'd like to make a progress on this proposal to resolve https://github.com/w3c/IFT/issues/259. I've summarized expected inputs and outputs here. I think this is still not comprehensive, appreciate your any feedback...

Yeah it makes sense consider generating a full URL. fyi, the reference library only supports pathname to generate a string tho. https://github.com/pillarjs/path-to-regexp#compile-reverse-path-to-regexp I'm wondering how we should handle the case...

The infra doc says we should not enforce specific limits on algorithm inputs with regards to their size, resource usage, or equivalent. https://infra.spec.whatwg.org/#algorithm-limits Close this issue, feel free to reopen...

Thanks for elaborating on that. Understood the root concerns. Not sure if [32KB](https://chromium.googlesource.com/chromium/src/+/main/docs/security/url_display_guidelines/url_display_guidelines.md#url-length:~:text=Chrome%E2%80%99s%20omnibox%20limits%20URL%20display%20to%2032kB%20(kMaxURLDisplayChars)) is a reasonable number since that is the displayed size in the Chrome’s omnibox, but 2MB is...

The polyfill is managed in https://github.com/kenchris/urlpattern-polyfill and should be claimed there, but this is valid. To [canonicalize a protocol](https://urlpattern.spec.whatwg.org/#canonicalize-a-protocol), it uses the result of running [basic URL parser](https://url.spec.whatwg.org/#concept-basic-url-parser). And in...