v-drag-over-target is not removed when the drop is ending in a nested drop target

[enver-haase]

Description of the bug

When vaadin/web-components#8476 was fixed, the fix unfortunately broke the case where a drop target is nested in (added to) another drop target.

Expected behavior

The application should work just like it did in 24.5.0 .

Minimal reproducible example

Versions

• Vaadin / Flow version: Vaadin 24.5.6

[probert94]

I am facing the same problem in Vaadin 24.4.20. In the version we used before (24.4.14) it was still working.
The class for nested drop targets is only removed when the drop happens on them. So if you drag over 4 nested drop targets and drop it on one of them, 3 still keep the class

[tepi]

Investigated the issue and indeed, this is a regression due to fixing vaadin/web-components#8476. The commit is reverted [here](https://github.com/vaadin/flow/pull/20822) and will trickle down to affected versions as well. So I'll close this ticket now and will re-open vaadin/web-components#8476 since it seems we need some other kind of fix for it.