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
The default width for the time input field when showTimeInput=true is currently set to 85pxin the src seen here which cuts the AM/PM text as seen in the screenshots below.
Screenshots
Firefox: 81.0.2 (64-bit)
Chrome: Version 88.0.4324.96 (Official Build) (x86_64)
Inspect the time input and compare to the screenshots above
Expected behavior
Input field displays all its content without cutting out any of its text.
I would suggest removing the 85px and let the browser decide the width necessary. This is what I'm doing in my override of the CSS using inline styles with
I am wondering if anyone else is experiencing this issue.
Desktop
OS: macOS Catalina, Version 10.15.7
Browsers
Chrome Version 88.0.4324.96 (Official Build) (x86_64)
Firefox 81.0.2 (64-bit)
Additional context
This seems to affect Firefox and Chrome. Safari V.14.0.1 shows a 24 hour clock so the AM/PM text is never there.
On mobile(iPhone SE) Chrome and Safari display the native time picker and 85px is more than enough to show all text content + it seems the iPhone has a smaller font-size for inputs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The default width for the time input field when
showTimeInput=true
is currently set to85px
in the src seen here which cuts the AM/PM text as seen in the screenshots below.Screenshots
Firefox: 81.0.2 (64-bit)
Chrome: Version 88.0.4324.96 (Official Build) (x86_64)
To Reproduce
Expected behavior
Input field displays all its content without cutting out any of its text.
I would suggest removing the
85px
and let the browser decide the width necessary. This is what I'm doing in my override of the CSS using inline styles withI am wondering if anyone else is experiencing this issue.
Desktop
Additional context
The text was updated successfully, but these errors were encountered: