Addison Phillips

discussed in 2025-03-10 call. closing because we have not received any feedback contrary to WG consensus to require all *

I think private-use annotations might be used for many different things. It will be up to the implementer to define what the private-use annotation is for, what it does, how...

I'm going to suggest that we not support private-use annotations with the registry syntax, at least in the 45 time frame. I am open to making this `Future` instead.

Marking for `Future`.

I think this is a non-starter? Our syntax is very consistent about optional whitespace: we are very lax when it's optional, especially inside expressions. The `{`/`}` are *never* part of...

We agreed to the syntax for 45 in the F2F. I'm going to mark this for consideration during tech preview.

I think some care should be exercised about how we discuss the whitespace here. If one just looks at the sigil, the spaces looks weird. But notice that in the...

The current syntax permits space between the bracket and the opening sigil (either `#` or `/`) and does not permit whitespace between the sigil and the identifier. We don't have...

We should also probably clarify in spec whether the descriptive information in the registry file is normative. Some of the MDN-borrowed text is phrased normatively (since it is normative in...

Moved to v46, since we made the registry.xml not part of preview.