misspelled-element-property

This fails the run. Where it is wrong about your code, // ramonda-check-ignore <reason> on the line says so, and the reason is printed on every run.

Reported when a name is written in the wrong case for element state that lives only in a property, so it is written as an attribute nothing reads.

A few pieces of element state live in a PROPERTY and have no attribute of that name at all: an <input>'s indeterminate, and a media element's volume, playbackRate and currentTime. There is no lowercase content attribute for these to be the HTML spelling of, so each has exactly one name and anything else is a different one.

Written in the wrong case it is not set at all. It goes into the document as an attribute instead, nothing reads it, and the element keeps whatever it had:

<video playbackRate={2} />   // sets the property
<video playbackrate={2} />   // writes playbackrate="2" and does nothing

The types accept both. RamondaArgs has an arm keyed on Lowercase<string> so that any real lowercase HTML attribute passes without being enumerated, and the wrong spelling goes through it — which is exactly why this is reported here instead.

None of this state survives a server render, whichever way it is spelled: there is nowhere in markup to put it, so it is set when the page hydrates. That is HTML's limit rather than the framework's.

Next

• All rules — the other checks this one runs beside.
• Checking your app — how to run it, and what it proves.