`.type` dont work with `datetime-local` inputs

• @testing-library/user-event version: 13.1.9

• Testing Framework and version: jest 27.0.5
• DOM Environment: jsdom (default jest version)

Relevant code or config

import '@testing-library/jest-dom/extend-expect'
import {render, screen} from '@testing-library/react'
import userEvent from '@testing-library/user-event'
import React from 'react'

const Input = () => {
  return <input type="datetime-local" data-testid="input" />
}

test('works properly', () => {
  render(<Input />)

  const value = '2000-01-01T00:00'
  const elInput = screen.getByTestId('input')

  expect(elInput).toBeVisible()
  expect(elInput).toBeEnabled()
  expect(elInput).toHaveValue('')

  userEvent.type(elInput, value)

  expect(elInput).toHaveValue(value)
})

What you did: tried to type a date to the datetime input

What happened: no date has been entered on the input

Reproduction repository: https://codesandbox.io/s/gifted-kapitsa-dfhst?file=/main.test.js

Problem description:

Suggested solution: I’ve seen previous similar issues (for date or time inputs), and I think it’s just a matter to include a branch logic for datetime-local inputs.

[ph-fritsche]

@Fox32 With consistent behavior across browsers we might consider an implementation. An issue collecting information on the browser behavior and discussing possible implementations would be welcome. The UI representation as used by the browser is not programmatically available. So an implementation would need to fill the gap between the (perceived) user interaction and the IDL properties.

[Fox32]

Looks like Firefox has support nowadays (https://bugzilla.mozilla.org/show_bug.cgi?id=1283388) and behaves similar to Chrome. Can we have another look at this issue?