| 07:01 | <annevk> | Lea Verou: well we do try to atomically update the HTML standard so I think we should try to identify all places in advance |
| 07:03 | <annevk> | akaster: looks like ECMAScript removed %IteratorPrototype% and nobody filed an upstream PR? (This is how we detect a subset of cross-specification "compilation" issues.) |
| 07:35 | <sideshowbarker> | sideshowbarker: though where does it say to use the 3 can only come from using the input value. If the spec doesn’t clearly require doing that, I guess it’s possible that other implementors — in order to get that test case to pass — may have just made an assumption about what the spec intended. |
| 07:40 | <sideshowbarker> | I mean, that test case is basically the same as what’s in Example 4 in the spec at https://w3c.github.io/accname/#example-4 — a I guess it’s possible that the spec used to state such requirements, but then they got inadvertently dropped in a later revision. |
| 07:44 | <sideshowbarker> | I’m intentionally avoiding to look at the existing code for any other implementations — so I can make sure it’s actually implementable as specced (without needing to make any assumptions that aren’t actually requirements) |