| 06:59 | <bakkot> | annevk (or whoever): is the process that I should now go file bugs for https://github.com/whatwg/fetch/pull/1753 against the various implementations? |
| 07:04 | <sideshowbarker> | bakkot: yeah, whatwg spec PR authors are the ones who typically raise the associated browser bugs for their spec PRs — unless somebody else has gotten to it before them |
| 07:07 | <bakkot> | ok cool |
| 07:08 | <sideshowbarker> | by the way, about the tests at https://github.com/web-platform-tests/wpt/pull/46198, isn’t an IDL test also needed? |
| 07:08 | <bakkot> | I guess I'll open the PRs for adding this method to Blob and PushMessageData also before filing |
| 07:08 | <bakkot> | sideshowbarker: I don't know what "an IDL test" means in this context |
| 07:09 | <sideshowbarker> | ah, gimme a second — I’ll get you a link |
| 07:09 | <bakkot> | I just grepped for arrayBuffer and added similar tests for bytes |
| 07:10 | <sideshowbarker> | https://github.com/web-platform-tests/wpt/tree/master/interfaces is what I mean |
| 07:11 | <sideshowbarker> | after changes get merged into the spec, those get automatically updated — but not for PRs |
| 07:12 | <sideshowbarker> | but maybe it’s not needed for PRs, I dunno |
| 07:12 | <bakkot> | yeah the readme/files claim the things in that directory are generated |
| 07:13 | <sideshowbarker> | right — they eventually get overwritten eventually at least |
| 07:14 | <sideshowbarker> | but an implementor working on implementing your change might want to have the interface/IDL tests for it to use while they’re working on the change |
| 07:14 | <sideshowbarker> | some projects sometimes land changes from PRs before they’re merged into the spec (WebKit does at least) |
| 07:16 | <sideshowbarker> | that said, I don’t know if other PR authors add the interface/IDLs WPTs in cases where they’re adding new methods to the spec |
| 08:13 | <Ms2ger> | Yeah, the bot will update the idl test once the spec is actually updated, so no manual work necessary |
| 10:43 | <keithamus> | I wonder if document itself should have something like getCaretRect(). It would return something reasonable no matter where the caret is - inside some UA widget or designMode or contenteditable |
| 12:54 | <Ms2ger> | So you can do (new Int32Array(10))[2], but I keep overlooking where the spec for this is. Does anyone have a pointer? |
| 13:14 | <arai> | is it about whether to treat the Int32Array constructor arguments as length or not? if so, https://tc39.es/ecma262/#sec-typedarray step 6.b vs 6.c |
| 13:59 | <Ms2ger> | No, the [2] indexing - sorry for the confusion |
| 14:14 | <arai> | then it's https://tc39.es/ecma262/#sec-typedarray-exotic-objects |
| 14:21 | <Ms2ger> | Thanks! I kept looking in Indexed Collections and not finding anything |