Anne van Kesteren
Anne van Kesteren
See https://github.com/shivanigithub/http-cache-partitioning/issues/2 and https://github.com/whatwg/fetch/pull/943 for some background. Currently the (proposed) prose allows for an additional key, but doesn't define what it is.
It seems like you currently cannot resolve a promise with another one. This came up in https://github.com/privacycg/storage-access/pull/70.
Currently we have this: > `[Exposed=*]` is to be used with care. It is only appropriate when an API does not expose significant new capabilities. If the API might be...
Complaining about conformance terms can be quite useful. Unfortunately I had to disable this as part of 37c0e6fe29c50d9c19842135f3f2b265ddcbe932 as it was rather hard to find all the violating instances (made...
Per https://github.com/heycam/webidl/pull/423#issuecomment-326332460 this exists. I'd like to study such usage and see if we can get rid of it.
Modern specification-prose will use https://infra.spec.whatwg.org/ data structures. E.g., an algorithm would return a list of JavaScript strings or a byte sequence. However, IDL does not work that way. It only...
> Specifications may reference the concept "|object| implements |interface|" > in various ways, including "|object| is an |interface| object". Can we try to settle on the one true way that...
As per https://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0330.html this is a mismatch with JavaScript. Fixing this is a little risky, but we've successfully changed exception types in the past which makes me hopeful. cc @littledan
I think we should give more advice to specifications how to deal with promises and realms. I think typically promises are created in the relevant realm of this. However, this...
I think the goal should be to map these to * byte sequence * JavaScript string * scalar value string as defined in the Infra Standard. We'll most likely need...