V18 PrimeNG styles in shadowDOM encapsulation components

[LMatass]

Hello,

I'm using primeng in a angular webcomponent which obviusly its using shadowDOM as view encapsulation. Currently primeng its creating the style elements in the main document body, is there the possibility to change the document where the styles are created? and introduce them instead on the shadowRoot element?

Currently I have a workaround which is based on:
A dom observer that listens for the style elements with data-primeng-style-id attribute. Whenever one of this elements its added, I copy the element into my shadowRoot element and remove it from the document.

Is there any plan to make flexible where do we want style elements to be created? if not, is there any other workaround?

[Khanaash]

Hi,

Any updates on this thread ? I'm experiencing microfrontends with webcomponent applications (under shadowdom) and i am facing the same issues. With prime 17, we can inject the prime css by including it in the angular webcomponent css but with v18, it is automatically loaded into the doc root.

Any recommandations or workaround would be appreciated. Thank you.

[LMatass]

Right now the only workaround I found is using an iframe but these breaks the benefits of webcomponents/microfrontends... Would be great if they would offer use the possibility to reference the doc where to insert the style elements...