Currently, if an item is filtered, the preventDefaults also prevent interaction with the item's children, such as editing an input. Is this intended? It feels like a bug to me. This may be somewhat related to this thread.
To reproduce:
Make a ReactSortable with filter="#filter"
Make some children, one of them with id="filter" and an <input> child
Attempt to move the filtered child, and it is unmovable (as expected)
Attempt to edit the filtered child's <input>, and it is not editable (not expected, should be editable)
Currently, if an item is filtered, the
preventDefault
s also prevent interaction with the item's children, such as editing an input. Is this intended? It feels like a bug to me. This may be somewhat related to this thread.To reproduce:
ReactSortable
withfilter="#filter"
id="filter"
and an<input>
child<input>
, and it is not editable (not expected, should be editable)