Closed yume-chan closed 1 year ago
The http-equiv attribute on <meta> element (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#http-equiv) and accept-charset attribute on <form> element (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form#accept-charset) are the only two exceptions in all HTML attributes that they use kebab case.
http-equiv
<meta>
accept-charset
<form>
dom-expression (and Solid) doesn't have any special handing for them (as opposite to React who accepts camelCase but emits kebab case), but the TypeScript definition for these two attributes are in camelCase and lower case:
https://github.com/ryansolid/dom-expressions/blob/a85d688353fef165b0456d5e192f4359dc00d5cb/packages/dom-expressions/src/jsx.d.ts#L989-L995
https://github.com/ryansolid/dom-expressions/blob/a85d688353fef165b0456d5e192f4359dc00d5cb/packages/dom-expressions/src/jsx.d.ts#L841-L853
The
http-equivattribute on<meta>element (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#http-equiv) andaccept-charsetattribute on<form>element (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form#accept-charset) are the only two exceptions in all HTML attributes that they use kebab case.dom-expression (and Solid) doesn't have any special handing for them (as opposite to React who accepts camelCase but emits kebab case), but the TypeScript definition for these two attributes are in camelCase and lower case:
https://github.com/ryansolid/dom-expressions/blob/a85d688353fef165b0456d5e192f4359dc00d5cb/packages/dom-expressions/src/jsx.d.ts#L989-L995
https://github.com/ryansolid/dom-expressions/blob/a85d688353fef165b0456d5e192f4359dc00d5cb/packages/dom-expressions/src/jsx.d.ts#L841-L853