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 dragging and dropping elements in the ui-editor the hoverstate is not changed. This means that the background of the element at the position of the dragged item is white and the Editbutton is still there. Problem is observerd i chrome, and widely discussed amoung react-dnd-users.
I think this is due to the fact that the view is using hover state to display these features instead of manualy using onMouseEnter / onMouseLeave and just propagate the hover-state to subcomponents manually displaying the items that should be showed:
There are several benefits of going with the non-css alternative. You get better control over components and how they are displayed and needless to say, its easier to make tools accessible. Its really the focus of an element that should display the buttons, not the hover state.
Its also easier to test, as the state could be showed programmaticly.
The text was updated successfully, but these errors were encountered:
When dragging and dropping elements in the ui-editor the hoverstate is not changed. This means that the background of the element at the position of the dragged item is white and the Editbutton is still there. Problem is observerd i chrome, and widely discussed amoung
react-dnd
-users.I think this is due to the fact that the view is using hover state to display these features instead of manualy using onMouseEnter / onMouseLeave and just propagate the hover-state to subcomponents manually displaying the items that should be showed:
There are several benefits of going with the non-css alternative. You get better control over components and how they are displayed and needless to say, its easier to make tools accessible. Its really the focus of an element that should display the buttons, not the hover state.
Its also easier to test, as the state could be showed programmaticly.
The text was updated successfully, but these errors were encountered: