François Daoust

> I do not know if this information is helpfull because I think these issues can only be fixed in the corresponding CSS specs One of the goals with webref...

> But I understand that you prefer not to hardcode exceptions. Right but the invalid syntax should be fixed. If you can report this issue as well to the CSS...

> But some values for the pointer-events property are only defined in SVG 2 and are supported in several browsers. I will downgrade to v3 for now but I will...

> I can use the main branch and keep my existing curation strategy. We probably cannot satisfy everyone but if you need to keep on using your own curation strategy,...

Starting with v4.2.1, the `@webref/css` includes fixes for the properties discussed above. > From this perspective, another issue related to CSS Fill Stroke, which has not been updated since 2017,...

> If [Filter Effects](https://drafts.fxtf.org/filter-effects-1/#typedef-filter-url) and [CSS Masking](https://drafts.fxtf.org/css-masking-1/#valdef-mask-image-url) were linking to the `` definition in CSS Values, would it prevent duplicate entries for this type in `@webref/css`? Does an open issue...

That looks good although it's not obvious to me that patches would improve the specs on top of making them more easily machine readable (that's great by itself, but not...

> For this case, the target should be an `HTMLFormElement`. What the event target should be doesn't depend on whether the event bubbles. (Terminology: when event handlers for other targets...

I prepared the updates to scripts in Webref to also produce `@webref/events` in a draft PR (#650), with a view to creating and running the tests that check on the...

> Is the benefit of this that it erases some silly cases where events are set to bubble even though there is no event path? Internally, yes, that allows us...