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
Regression (a behavior that used to work and stopped working in a new release)
Current behavior
When a component is initially rendered in edit mode and user puts in data without clicking the component, the mode does not go back to edit mode automatically when focus is switched to another editable component. It works as expected only if user also clicks on the component before focus is switched.
See the screenshot below.
Note: The editable component on the left with text "test" is still in edit mode even though the focus is now on the other editable component (on the right)
Expected behavior
The mode should go back to view mode automatically for editable components that are initially rendered in edit mode once the component does not have the focus anymore.
Minimal reproduction of the problem with instructions
No response
What is the motivation / use case for changing the behavior?
No response
Environment
No response
The text was updated successfully, but these errors were encountered:
I'm submitting a
Regression (a behavior that used to work and stopped working in a new release)
Current behavior
When a component is initially rendered in edit mode and user puts in data without clicking the component, the mode does not go back to edit mode automatically when focus is switched to another editable component. It works as expected only if user also clicks on the component before focus is switched.
See the screenshot below.
Note: The editable component on the left with text "test" is still in edit mode even though the focus is now on the other editable component (on the right)
Expected behavior
The mode should go back to view mode automatically for editable components that are initially rendered in edit mode once the component does not have the focus anymore.
Minimal reproduction of the problem with instructions
No response
What is the motivation / use case for changing the behavior?
No response
Environment
No response
The text was updated successfully, but these errors were encountered: