04:28
<Thad Guidry>

Hello, I'm using ReSpec and trying to reference the 2 concepts that I thought would already be part of Webref (xref) indexing and/or even Infra.
MUST - aka REQUIRED
MAY - aka OPTIONAL

I know from RFC2119 that these have been around forever. But I was honestly surprised that even with those terms used in Infra docs itself and 1000's of other standards, that those 2 concepts are not indexed?

The reason I would have thought they would already be part Webref was that they come into play when describing parameters or arguments that are either REQUIRED or OPTIONAL.

How can I help make the concepts of RFC2119 (and the concepts aliases) as part of Webref or Infra , so that in ReSpec I could simply refer to them via the Shorthand syntax of [=OPTIONAL=] and [=REQUIRED=] ?

05:28
<sideshowbarker>
Thad Guidry: Seems like you can do that already by using the English prose words must and should — rather than needing to type an [=OPTIONAL=] and [=REQUIRED=] macro thing
06:23
<By Sineks>
hi
06:23
<By Sineks>
css3 için "backroung-opacity" özelliği gelecekmi?
06:24
<By Sineks>
Will the "backroung-opacity" feature come to css3?
20:52
<Andreu Botella>
I'm looking at custom element reactions. Is my understanding correct that every time that JS code could trigger a CE reaction, it is through a [CEReactions] WebIDL method? And the only times where the reactions are run in a microtask are when they're caused by user interaction with no JS code in sight?