-
Notifications
You must be signed in to change notification settings - Fork 157
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
Support: Web components with shadow dom #15
Comments
Thanks @rstoneIDBS. Here is a potential plan of attack:
|
Hi @alexreardon , this is something I might be able to look into but it is going to take some time as I'm pretty busy with other things. We were investigating adding some drag & drop features to a PoC but have now moved on from that so its not a priority for us at the moment. |
If somebody is willing to put together our board example with web components that leverages shadow dom, I can take a look at adding support to pdnd :) |
Thanks for your original PR @rstoneIDBS. I suspect there is not a whole lot we will need to do to get things working. I am not confident enough with web components right now to successfully make the changes required. It would be great to get the assistance from the web components community for this one. |
Relevant data points:
|
@alexreardon - I would like to be able to help out here, but at the moment I just don't have the bandwidth :( |
Here's the list example with web components and tailwind. https://github.com/driskull/pdnd-web-component-tailwind |
Looking at the code in "element-adapter.js":
If the dragged element is contained within the shadow root of another web component then 'target' above won't be the element being dragged but will instead be the web component due to event re-targetting. The following code sandbox shows the issue:
https://codesandbox.io/p/sandbox/pdnd-web-components-forked-l8f6tv
The text was updated successfully, but these errors were encountered: