| 03:17 | <devsnek> | [SameObject] just means that accessing the property should always give the exact same object right? |
| 03:50 | <annevk> | devsnek: yeah, though we want to replace it with [Cached] or some such to make it more useful for spec authors |
| 17:40 | <luxio> | does whatwg have affiliation/involvement with schema.org |
| 18:38 | <domfarolino> | Domenic: when we say “let X be the current state of the ‘crossorigin’ attribute” does this imply that X will definitely be one of the valid CORS Settings Attributes or does anything go? |
| 18:39 | <Domenic> | domfarolino: it will definitely be in one of the three states listed in https://html.spec.whatwg.org/multipage/urls-and-fetching.html#cors-settings-attributes (Anonymous, Use Credentials, or No CORS) |
| 18:39 | <Domenic> | According to the rules of that table + invalid value default + missing value default |
| 18:40 | <Domenic> | Last two paragraphs of https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#enumerated-attribute give the detailed rules |
| 18:51 | <domfarolino> | Domenic: Ah perfect, thanks! That’s what I was thinking but “current state” threw me a little; I wasn’t sure if that sort of parsing was taking place implicitly |
| 18:57 | <Domenic> | Yeah, maybe "current state" would be best linked to something |
| 19:00 | <domfarolino> | Yeah, that or “limited to only known values” similar to the IDL getter but maybe the message is already clear enough hmm |