You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote a test(a5ec800) to check for existence for attributes specified in Attributes.hx and noticed that meta#charset is actually not a property of the "meta" DOM element in JS.
SO says so:
there is no property that reflects the charset content attribute.
How does renderers use these attribute specs? Do they .attr = value or .setAttribute(attr, value)? For example, I see there is role in GlobalAttr. I am pretty sure element.role = value is basically meaningless, because .role is not a JS property and changes will not be reflected to the actual DOM. On the other hand, element.setAttribute('role', value) would manipulate the DOM as-is so it could be picked up by css selectors.
I would like to ask: should we include non-JS-prop attributes in the spec?
We should probably decorate all attributes that don't have a corresponding property as such, then any libraries can leverage that. For coconut.react-dom it's probably fine already, because react/preact deal with this, coconut.html uses attributes anyway and coconut.vdom can pick the infos from here.
I wrote a test(a5ec800) to check for existence for attributes specified in
Attributes.hx
and noticed that meta#charset is actually not a property of the "meta" DOM element in JS.SO says so:
https://stackoverflow.com/a/12560258/3212365
The text was updated successfully, but these errors were encountered: