Does this lib support <input type="color"/> ?

[ambroiseRabier]

Does this lib support <input type="color"/> ?

[kentcdodds]

Hi @ambroiseRabier,

Yes it does.

[ambroiseRabier]

I didn't said it explicitly, but how do you use this library to set the color ? I doesn't type anything, when choosing a color, it is a serie of minimum 2 clicks. Neither click or type seem to have options for colors.
I just tried the closest I could think of: userEvent.type(element, '#123456', {delay:0}), no success with that.

[kentcdodds]

Sorry, I think I was mistaken. Hey @visualjerk, do you have any ideas here?

[visualjerk]

<input type="color" /> is a bit tricky, as most browsers display it as a color picker.

As you can see here typing on these doesn't trigger an input event or change the inputs value.

So in order to test those you would probably have to use dom-testing-library fireEvent to dispatch an input event:

fireEvent.input(colorInputElement, {target: {value: '#333333'}})

Maybe we find a solution that comes closer to how a user interacts with these kind of inputs, but I assume it is pretty hard to do inside an emulated dom.

[kentcdodds]

I agree. Maybe we could add a note in the docs about this? @ambroiseRabier, would you be interested in doing that?

[ambroiseRabier]

@visualjerk that is indeed the solution I went for.
@kentcdodds when you mean doc, you mean the README.md ? I see no section that would fit this piece of information, should we add a "Known issues" or "Unsupported user events" section ?

[kentcdodds]

Yeah, I think a new section titled "Known issues" or "Known limitations" would be useful.

[jesujcastillom]

Can I help with that?

[kentcdodds]

Sure @jesujcastillom :)

[josebui]

Is there any expectation to support this in the future?