When I define ‘area’ in the DragSelect settings, it seems that the non-selectable html elements that are inside the defined DragSelect area, which are listening to native events (click, mouse down, etc) are having those native events blocked or intercepted by DragSelect. They aren’t firing at all. This is only an issue on iPad Safari and Chrome, but not on Desktop. If I don’t define an area, all elements that aren’t selectable on page are having their events not fire. Anybody seen this before or have an idea what might be causing it?
Hi @clementrcheng thank you for using the library ❤️
And thanks for reporting this, sounds like a bug indeed, if you have time, a contribution is welcome. Otherwise I’ll have a look as soon as time permits.
When I define ‘area’ in the DragSelect settings, it seems that the non-selectable html elements that are inside the defined DragSelect area, which are listening to native events (click, mouse down, etc) are having those native events blocked or intercepted by DragSelect. They aren’t firing at all. This is only an issue on iPad Safari and Chrome, but not on Desktop. If I don’t define an area, all elements that aren’t selectable on page are having their events not fire. Anybody seen this before or have an idea what might be causing it?
Thanks in advance!