François Daoust

> A lot of this is non-standard, but at least these events that are missing from the webref data: > > * `VisualViewport` events That's a bug in CSSOM View,...

I think we're going to need to somehow rename one of the `` definitions, e.g. the one in SVG 2 to something like `` or the one CSS Fill Stroke...

Webref contains the data needed to create the warnings. We've split Reffy's codebase into two parts not long ago: Reffy in itself being the crawler and [Strudy](https://github.com/w3c/strudy) being the analyser....

I think the whole purpose of this exploration is to converge on one list of features and understand how it can map to the implementation information that exists on the...

Here is a first dump of exported terms defined in more than one spec. This is the result of parsing the `dfns` extracts with the following rules: 1. Only consider...

Note code that produces the previous report is in a dedicated Reffy branch: https://github.com/w3c/reffy/blob/study-dfns/src/cli/study-dfns.js

Thanks @cdoublev, I moved your comment to a dedicated issue #563.

Not exactly as smooth as you might want it to be, but "something" nevertheless: the `curated` branch now has a package.json file. This allows you to do: ``` npm install...

The formal syntax is missing because the spec currently does not follow the usual syntax conventions used in CSS specs to define properties. For instance, the table that defines `math-style`...

This and other event-related information are being tracked in https://github.com/w3c/reffy/issues/772. One difficulty is that this information only exists in spec prose, making it hard to extract it automatically.