-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clicking on YesNoSelectEditor behavior has changed since 5.4.1 #937
Comments
It's working fine on the example-frozen-columns, with oh actually, I had to read your issue multiple time to understand your problem. It wasn't clear that the issue is not to open it but instead happens when trying to click the select dropdown itself. EDIT Actually I found that the regression was introduced in v5.4.1 by PR #897, when the cell was clicked it went into the new code thinking the user wanted to start a dragging and it cancelled event bubbling so clicking the dropdown had no effect |
- a previous PR #897 caused a regression on a cell with a select dropdown (like `Slick.Editors.YesNoSelect`), the regression was caused by the implementation of Draggable `allowDragFromClosest` which will check if current DOM element is `.slick-cell` or if not it will also try its ancestor and that caused the regression because the cell with the editor also had a `.slick-cell` and so the code taught that the user started a drag and it cancelled event bubbling which in turn also prevented the select dropdown to be clickable. - to fix this issue we need to make sure that the cell is queried not just with `div.slick-cell` but also with certain CSS classes, we need to check if it has either `.dnd` or `.cell-reorder` to permit the dragging
@ghiscoding |
fixed in v5.5.6 |
Behavior of before version 5.4.0
The select element shows options when clicked.
Behavior of after version 5.4.1
The select element doesn't show options when clicked. (It shows options only when the space key is pressed.)
Reproduction code
When we replace versions from 5.5.5 to 5.4.0, the behavior seems to change.
The text was updated successfully, but these errors were encountered: