You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I click on the inner padding around the input inside of a text field I expect it to focus on the input.
However, the focus is on the field itself leaving either the input unselected if it's empty or fully selected if it's not, like you tabbed into it.
It's possible this change in behavior was caused by a browser update as the current version of Firefox (135) does not exhibit this behavior and I do not recall older versions of Chrome doing this either but I don't know which version specifically.
Chrome 132 appears to be the last working version, meaning 133 is what broke it. Now we just have to figure out if this was an intentional breaking change or a regression. My first thought was this: https://chromestatus.com/feature/5134341540413440
What is affected?
Accessibility, Component
Description
When I click on the inner padding around the input inside of a text field I expect it to focus on the input.
However, the focus is on the field itself leaving either the input unselected if it's empty or fully selected if it's not, like you tabbed into it.
It's possible this change in behavior was caused by a browser update as the current version of Firefox (135) does not exhibit this behavior and I do not recall older versions of Chrome doing this either but I don't know which version specifically.
Reproduction
https://material-web.dev/components/text-field/
Workaround
I have not found a workaround.
Is this a regression?
Yes. This used to work, but now it doesn't.
Affected versions
Failing in 2.2.0, worked in 2.2.0
Browser/OS/Node environment
Browser: Chrome 133.0.6943.127
OS: Windows 11
Node version: 22.13.1
npm version: 11.1.0
The text was updated successfully, but these errors were encountered: