02:11 | <domfarolino> | https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload:attr-link-referrerpolicy mentions that changing `as`, `crossorigin`, and `referrerpolicy` triggers new requests for some relations, but I don't believe that is the case for `as` or `referrerpolicy`? |
02:11 | <domfarolino> | Should the list https://html.spec.whatwg.org/multipage/links.html#link-type-stylesheet:fetch-and-process-the-linked-resource reference `as` and `referrerpolicy` attrs manipulations? |
02:29 | <Domenic> | domfarolino: hmm, interesting... It seems like it probably should for at least `referrerpolicy`, although I believe `as` is only applicable for preload? Although similarly I don't see any spec text to mandate re-fetching a `<link rel="preload">` when its `as=""` changes... |
02:33 | <domfarolino> | Domenic: Ah, yeah `as` should only be for preload. But yeah, probably both sections should reference `referrerpolicy`, and preload should additionally `as`. Though I wonder how UAs handle these mutations |
02:34 | <Domenic> | Right, always the question :-/ |
02:43 | <domfarolino> | Domenic: Also does "set, changed, or removed" include going from attr="value" to attr="value" (i.e., "setting" the same value)? |
02:46 | <Domenic> | domfarolino: no, per https://html.spec.whatwg.org/multipage/infrastructure.html#dom-trees |
02:47 | <domfarolino> | perfect, thanks! |
08:03 | <annevk> | Domenic: hmm so we do create mutation records and run attribute change steps, so I suspect it depends and needs to be tested |
08:03 | <annevk> | domfarolino: ^ |
13:33 | <zcorpan> | innovati: tag is a syntax construct. element is a DOM concept. what happens with a tag depends very much on the context where it's found by the parser |