| 00:32 | <Domenic> | Could I get bug edit permissions on whatwg/html for labelling issues? |
| 00:50 | <sideshowbarker> | jub0bs: If you raise bugs and Cc me, I would be happy to write browser patches for adding warnings or improving existing ones. And while we’re at it, I think we should also try to get a patch landed to make Chrome stop emitting the “If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled" message. …because to 99.99% or whatever of web developers, that message is in practice the complete opposite of being helpful to them. |
| 09:29 | <jub0bs> | sideshowbarker: Thanks for your reply. I'll open a couple of bugs asap. True about 'no-cors': many people believe that setting their request's mode to 'no-cors' will magically resolve their CORS issues. Perhaps this part of the error message is more misleading than helpful. |
| 10:07 | <zcorpan> | jub0bs: yeah, saying it was blocked by the same-origin policy would make more sense |
| 10:08 | <zcorpan> | But in the end the message should probably suggest reasonable options |
| 11:55 | <smaug> | https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes:reflected-idl-attribute-31 is somehow oddly written |
| 12:27 | <smaug> | first there are some items, and after them actual getter and setter steps. But what is for example the first item? Is that part of some algorithm or is it not? |
| 13:12 | <annevk> | smaug: the first list item is introducing a shorthand, used in the remaining list items for defining infrastructure |
| 13:13 | <annevk> | I do agree it's a bit strange, but I also wasn't sure how to refactor it when I last fixed some reflecting stuff. |
| 14:32 | <Dominic Farolino> | https://html.spec.whatwg.org/C#becomes-connected happens when the insertion steps for an element are called and it is "connected". But can the insertion steps ever be called for an element that's disconnected? |
| 15:44 | <Jake Archibald> | Folks who are familiar with delegatesFocus… what are the use-cases? Is it much different to putting everything in the shadow root in a <label> pointing to the field? |
| 17:15 | <keithamus> | Jake Archibald: or a custom button or similar. |
| 17:17 | <keithamus> | https://github.com/muan/input-duration-element an example in the real world. |
| 17:21 | <Jake Archibald> | Yeah, support for .focus() is nice. I guess I don't always want the "clicking anything in the shadow root delegates focus to one element" thing |