| 15:16 | <Domenic> | annevk: does https://github.com/w3c/css-houdini-drafts/issues/473#issuecomment-711733408 mean "close with no action"? I still don't understand the issue that well... |
| 16:54 | <annevk> | Domenic: yeah, but I didn't close it to see if someone had a different take |
| 16:54 | <annevk> | Domenic: in particular I wonder if wanderview agrees |
| 16:56 | <Domenic> | annevk: makes sense. Will leave open for a bit at least... |
| 17:00 | <annevk> | "I think they communicate errors out via onprocessorerror." So there's no need for integration with "report an error" whatsoever? I guess there might not be a lot of callers... |
| 17:13 | <Domenic> | annevk: yeah, I mean, there might be room for improving the formalization of the web audio spec in that regard, but right now they seem to wrap a bunch of potentially-erroring things in a spec try/catch and forward the errors. |
| 21:45 | <wanderview> | annevk: domenic: I don't have any objections at this point |
| 21:45 | <Domenic> | Cool, thanks! |
| 21:49 | <TabAtkins> | Domenic: I'm doing some Bikeshed fixes, and as part of it I'm going to have a minor behavior change that'll affect the Streams spec. I'll submit the PR, but there's no reasonable transitional form that'll work both pre- and post-change. Do you want to me to wait on pushing the Bikeshed fix until you've merged the PR, or are you okay with me pushing now and you merging the fix after? |
| 21:49 | <TabAtkins> | (The change is just that some links will break until you apply the fix.) |
| 21:49 | <Domenic> | TabAtkins: OK either way. |
| 21:50 | <TabAtkins> | kk |