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 hovering over help buttons used in different Field-components, which fields/components that gets a bold outline is different(behaving differently).
Images:
Here the field to the right(phone number) also has a bold border when hovering the help button.
In the screenshot above, the input field does not have a bold border when hovering the help button.
In this last screenshot, the input field also gets a bold border when hovering the help button.
langz
changed the title
bug(Field): help property behaves differently when hovered over in different Field component it's used in.
bug(Field): help property behaves differently when hovered over in different Field components
Dec 7, 2023
What should the expected behaviour be here? Should the input/inputs all be highlighted on suffix hover, if the suffix is clickable, or should it just be the suffix, to indicate that the click will only interact with the suffix? I feel like the input hover effect makes more sense when hovering over the label, vs the suffix 馃
馃悰 Bug Report
When hovering over help buttons used in different
Field
-components, which fields/components that gets a bold outline is different(behaving differently).Images:
Here the field to the right(phone number) also has a bold border when hovering the help button.
In the screenshot above, the input field does not have a bold border when hovering the help button.
In this last screenshot, the input field also gets a bold border when hovering the help button.
Video:
Screen.Recording.2023-12-06.at.13.15.02.mov
To Reproduce
This CSB is using
main
branch as of today, 06.12.2023.https://codesandbox.io/p/sandbox/eufemia-starter-forked-t9nshg?file=%2Fsrc%2FApp.tsx%3A91%2C51
One more CSB:
https://codesandbox.io/p/sandbox/eufemia-starter-forked-dfjxy3?file=%2Fsrc%2FApp.tsx%3A5%2C11
Steps:
The text was updated successfully, but these errors were encountered: