| 00:11 | <jsbell> | gsnedders: document.documentElement.appendChild(document.createElement('style')).innerText = 'body { background-color:red }' ? |
| 00:11 | <gsnedders> | jsbell: can you find anything in any spec that justifies that working? |
| 00:12 | <gsnedders> | (I realise that's a very different question :)) |
| 00:14 | <jsbell> | Heh.... um... |
| 00:15 | <jsbell> | Which part? document.documentElement, or createElement('style'), or setting its innerText ? |
| 00:20 | <jsbell> | To which I'd say https://dom.spec.whatwg.org/#document-element and https://html.spec.whatwg.org/multipage/semantics.html#the-style-element but I'm guessing you have a more subtle question |
| 00:20 | <jsbell> | and that's where my knowledge bottoms out. Also heading out, so TTFN and good luck! |
| 00:41 | <gsnedders> | jsbell: nah, I meant where the stylesheet is applied to the document |
| 01:20 | <Domenic> | gsnedders: https://html.spec.whatwg.org/multipage/semantics.html#update-a-style-block seems to apply whenever the element's child text contents are changed |
| 01:21 | <gsnedders> | ah, right, that does actually do everything looking again |
| 01:21 | <gsnedders> | somehow my glance missed that |
| 01:29 | <Domenic> | https://github.com/whatwg/html/issues/2997 being still unfixed seems bizarre to me |
| 01:33 | <gsnedders> | in a sense, I presume it's just a matter of editorial time given unlike many things, it's something there's at least decent interop on? |
| 01:38 | <gsnedders> | and CSS always seems to have way more constraints on editorial time than any other part of the platform |
| 01:45 | <devsnek> | how might one go about limiting the resolution of performance.now() to fit into 20 microseconds |
| 05:27 | <domfarolino> | yoav: http://crrev.com/c/1116418 is a little big (WIP). If you've any advice on splitting it up that'd be great but since it requires shuffling a lot around at once I don't think there's much room |
| 05:27 | <domfarolino> | yoav: http://crrev.com/c/1116418 is a little big (WIP). If you've any advice on splitting it up that'd be great but since it requires shuffling a lot around at once I don't think there's much room |
| 05:28 | <domfarolino> | oops. Thought I was in #chromium my bad |
| 06:22 | <zewt> | grumble grumble no way to reliably refresh a page without flushing cache |
| 06:48 | <yoav> | is there documentation to the HTML spec's syntax? e.g. what are the different `data-x` attributes and what they do? |
| 06:49 | <yoav> | I'm hitting some trouble trying to wrap an external definition with <code> and would love to understand if there's some way for me to indicate the compiler that it's an external ref |
| 07:17 | <domfarolino> | yoav: I believe the data-x attributes on things like <code> reference the data-x attributes defined on a <dnf> somewhere locally. |
| 07:20 | <domfarolino> | yoav: So I think you would use something like `<code data-x=someDfn>something here</code>`, and later on write `<dfn data-x=someDfn data-x-href=https://link-where-someDfn-can-be-referenced.com></dfn>` to link usages of `data-x=someDfn` with the external reference |
| 07:40 | <yoav> | OK, so I have to include an explicit dfn somewhere? |
| 07:55 | <domfarolino> | That's what all of the examples I see seem to indicate, but that feels a little funny. I'm guessing the explicit local `<dfn>` is not necessary if what you're referencing is exported from the spec it belongs to. What are you referencing? |
| 08:18 | <yoav> | domfarolino: referencing IETF RFCs (client hints) |
| 08:18 | <yoav> | I caved and just added a local dfn :) |
| 08:29 | <domfarolino> | haha, seems to be a good call though probably you'll find out for sure upon review |
| 13:58 | <Domenic> | OK I'm going to break down and document Wattsi syntax... |
| 14:44 | <Domenic> | Reviews (and suggested additions) appreciated: https://github.com/whatwg/wattsi/pull/79 |
| 14:55 | <yoav> | Domenic: thanks for documenting it! :) I'm in a full day meeting now, but will review tomorrow morning |
| 15:31 | <TimothyGu> | just to be sure: a document returned from DOMParser is not an active document, right? |
| 15:43 | <Domenic> | TimothyGu: I am 95% sure |
| 15:44 | <Domenic> | Yeah OK, checked definitions, 100% sure |
| 15:44 | <Domenic> | It has no browsing context, and no browsing context ever has it |
| 15:44 | <TimothyGu> | Okay cool |
| 15:44 | <domfarolino> | Wooo Wattsi syntax docs! |