search

vaadin / flow-components

Java counterpart of Vaadin Web Components
81 stars 63 forks source link

TextArea blocks input in Chrome and Edge browsers #6361

Open Izum-si opened 2 weeks ago

Izum-si commented 2 weeks ago

Describe the bug

In some Chrome or Edge browsers Vaadin Flow's TextArea blocks keyboard input as if the control was disabled: instead of input area only a grey rectangle is visible and the control can't even be focused.

Our users started noticing in Chrome this start of May, but it's in the last couple of weeks that the reports became more frequent and the problem apparent in Edge as well.

Firefox has no such problem.

Expected-behavior

Input enabled and characters can be input to TextArea from keyboard.

Reproduction

The same happens in the demo projects as well: https://vaadin.com/docs/latest/components/text-area

It doesn't happen in every Chrome/Edge browser though. Some of our users have this problem, others don't. As far as we were able to determine, it never happens if the Guest browser profile is used, nor if the browser is run with all extensions disabled (that is, with command switch --disable-extensions). Disabling extensions one by one, doesn't help however.

System Info

Windows 10, 11. Chrome v125.0.6422.142, Edge v125.0.2535.92 (also in earlier versions of both browsers - not sure exactly from which version)

ZheSun88 commented 2 weeks ago

I have Edge v125.0.2535.92 and Chrome 125.0.6422.142 on Windows 11.

i am NOT able to reproduce the issue mentioned here. I move the ticket to flow-components repo for further investigations

sissbruecker commented 1 week ago

I also couldn't reproduce the issue on either Windows 10 or 11, with either Chrome or Edge.

Since you mentioned that the component looks different when it doesn't work, a screenshot might be helpful. Otherwise there isn't much to go on here.

Izum-si commented 1 week ago

As I already said, this only happens in some browsers (could be tied to some extensions - since disabling extensions completely solves the problem - but we haven't been able to determine which of them or why). I'll ask our users whom reported the problem to take some screenshots and will post them here, when I get them. Meanwhile, I'm sure you'll get similar reports from other Vaadin users, since quite a few people use Chromium-based browsers and some are bound to have a "winning" combination of settings that causes this.

sissbruecker commented 1 week ago

You might then also want to collect information about which extensions are installed, from the available information these currently look like the most likely candidate for causing the issue.