I created this repo which uses your element and attribute reference libraries to do an audit of this library in the browser. It creates an element of "tag", then tests that the property lookups actually exists on the DOM object.
I did split the attribute tests into custom (element specific), global, and arai. Skipped event names and data- as they are well-known exceptions.
I set up vitest to run the tests in chrome, firefox, edge, and safari. With a bit of research, bucketted things into:
remove (deprecated)
not yet implemented (newer stuff)
corrections (spelling change)
attribute only (no DOM property)
I did html, still need to do svg.
Mostly wanted to provide an FYI. I found some bad data in html-element-attributes, will put issue there.
How’s it going? Did you want me to look into your repo, or were you planning to report back when you have more time? Should the core of your repo—testing actual browsers—be pulled into this project?
Hey there @wooorm 👋 Finally got back to following up on my comment about DOM props
I created this repo which uses your element and attribute reference libraries to do an audit of this library in the browser. It creates an element of "tag", then tests that the property lookups actually exists on the DOM object.
I did split the attribute tests into custom (element specific), global, and arai. Skipped event names and
data-
as they are well-known exceptions.I set up vitest to run the tests in chrome, firefox, edge, and safari. With a bit of research, bucketted things into:
I did
html
, still need to dosvg
.Mostly wanted to provide an FYI. I found some bad data in
html-element-attributes
, will put issue there.