| 10:24 | <smaug____> | annevk: do I recall correctly that focus handling is pretty much the only thing in Shadow DOM spec which hasn't been merged to elsewhere? |
| 10:26 | <annevk> | smaug____: yeah, kochi wanted to fix that iirc |
| 10:27 | <annevk> | smaug____: maybe also some event stuff? |
| 10:28 | <smaug____> | just trying to figure how to implement this all |
| 10:28 | <smaug____> | or where to look at what to implement |
| 10:30 | smaug____ | is about to start to update wchen's patches |
| 10:46 | <annevk> | smaug____: okay, another thing I realized is that https://w3c.github.io/DOM-Parsing/ isn't updated |
| 10:47 | <annevk> | smaug____: I'll look into and create a new tracking issue on upstreaming if we don't have one already |
| 10:48 | <smaug____> | annevk: what should be updated there? |
| 10:49 | <annevk> | smaug____: ShadowRoot.prototype.innerHTML is a thing iirc |
| 10:50 | <annevk> | smaug____: https://github.com/w3c/DOM-Parsing/issues/21 |
| 10:50 | <smaug____> | aha, I thought DocumentFragment had innerHTML in some spec |
| 10:51 | <annevk> | smaug____: that was a plan at some point, but didn't happen |
| 10:51 | <annevk> | smaug____: putting it on DocumentFragment is more complicated because there's no context node |
| 10:52 | <smaug____> | and what is the context node in ShadowRoot case? the host? |
| 10:52 | <annevk> | smaug____: yup |
| 10:58 | <annevk> | smaug____: https://github.com/w3c/webcomponents/issues/377#issuecomment-250693594 |
| 10:58 | <annevk> | smaug____: I added a comment there asking some questions from hayato |
| 10:58 | <annevk> | smaug____: and added a couple pointers to some issues I'm aware of |
| 10:58 | <annevk> | smaug____: hope that helps |
| 11:09 | <annevk> | smaug____: looking through things it seems like there's still many open issues around shadow trees that have gone unresolved |
| 11:12 | <ondras> | hm, can an AudioBuffer instance be passed to a Worker ? |
| 11:17 | <ondras> | DOMException: Failed to execute 'postMessage' on 'Worker': An object could not be cloned. |
| 11:17 | <ondras> | okay, apparently not. |
| 11:31 | <annevk> | gsnedders: see https://github.com/w3c/webcomponents/issues/78 for the >>>-controversy |
| 13:36 | <gsnedders> | is the private mailing dead and buried along with any notion of membership gone? |
| 14:04 | <annevk> | JakeA: did anyone sign up to remove foreign service workers from Fetch? |
| 14:04 | <annevk> | JakeA: there doesn't seem to be a tracking issue against Fetch either; I can probably write a patch though |
| 14:05 | <JakeA> | annevk: as in browsers or spec? |
| 14:05 | <JakeA> | There's https://github.com/w3c/ServiceWorker/issues/1188 for the spec |
| 14:05 | <annevk> | JakeA: spec, there's a bunch of text in Fetch |
| 14:06 | <JakeA> | annevk: it's on my todo list, but happy for you to do it |
| 14:06 | <annevk> | JakeA: I'm a little bit afraid of creating a bunch of rebase conflicts for your abort work whenever I touch Fetch |
| 14:07 | <JakeA> | annevk: I can deal with those. Going to do another push on the abort spec tomorrow. The whole thing's been like pulling on a thread, especially given that XHR needs changes now :( |
| 14:08 | <annevk> | JakeA: yeah, none of it was really in shape yet and the API really lays that bare |
| 14:09 | <annevk> | JakeA: this is why I try to advocate we first revamp existing things; e.g., with the storage work you're planning |
| 14:10 | <annevk> | But what typically happens is that folks add new features and the infrastructure is left broken for quite a while... Glad that's not the case here though |
| 14:11 | <JakeA> | gotta do it properly :D |
| 20:49 | <zcorpan> | yay https://github.com/w3c/csswg-drafts/commit/371d0a1e60e8a2045393fc4db2f1110b9418b2f2 |