TypeScript JSX focus events don't have consistent case about preact

[marvinhagemeister]

Are you saying that JSX should be using all lowercase instead, and the definitions in jsx.d.ts don't really matter?

No, I was just giving historical context. We should support lowercased events like they are specced in web standards + camelCase. Might just be a matter of updating the type definitions in our JSX types.

[marvinhagemeister]

FYI: Preact supports all lowercase event name to align with the web. I think the Capture suffix is because of a check in our source for capture events that's case sensitive. Might make sense to loosen that restriction. Off the top of my head I'm not sure if we support camelcasing them all natively or only in compat. Something worth to check.

[CodingDoug]

@marvinhagemeister VSCode gives me an uncomfortable error if the JSX attribute doesn't match exactly. For example:

Type '{ children: Element[]; id: string; class: string; onFocusin: undefined; }' is not assignable to type 'HTMLAttributes'.
Property 'onFocusin' does not exist on type 'HTMLAttributes'. Did you mean 'onfocusin'? ts(2322)

[marvinhagemeister]

Yeah onFocusin is something we'll never support. In your original message you wrote onFocusIn (note the uppercase letter I). Where is this new form of casing coming from?

[CodingDoug]

In my original message, I suggested that the definitions for these event attributes are incorrectly cased compared to the rest of the event attributes (scan the entire list in the file I cited - every single one of them is camel cased except for four of the focus events). I suggested alternatives that would bring them into consistency.

I think I may have been unclear after that - I'm not saying that I want to use onFocusin. I want to use camel cased attributes as they are defined in jsx.d.ts. Are you saying that JSX should be using all lowercase instead, and the definitions in jsx.d.ts don't really matter?