Open nwhittaker opened 2 weeks ago
This is because the drag and drop styles are included in the global calcite.css
file. Since that file isn't included in the shadow DOM of the shadowed component, they aren't displaying correctly.
The way to work around this would be to include the calcite.css
file within that shadow DOM.
We can potentially move these styles to each component that needs them. It would require some testing. cc @jcfranco @geospatialem
Check existing issues
Actual Behavior
Given a drag-enabled
<calcite-list>
element nested inside a custom element's shadow DOM, drop zones appear unstyled when dragging a list item.Expected Behavior
Drop zones retain their original styling.
Reproduction Sample
https://codepen.io/nwhittaker-esri/pen/bGXLQbN
Reproduction Steps
Reproduction Version
1.13.2
Relevant Info
No response
Regression?
No response
Priority impact
impact - p2 - want for an upcoming milestone
Impact
Impact is towards how effectively a custom component can be encapsulated. When containing a draggable list, this issue essentially eliminates using the shadow DOM as an option when constructing the component. However, foregoing the shadow DOM increases the risk of
id
collisions and external styles/scripts negatively impacting the custom component's UI/UX.Calcite package
Esri team
ArcGIS Field Apps