You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is likely not a Stencil issue, but rather some sort of conflict between Stencil and Angular. Still, since @stencil/angular-output-target exists I'd expect component to work properly in both shadow and non-shadow modes, or this issue be documented. Also, default slots do work, so there could be a solution/workaround on Stencil's side.
The text was updated successfully, but these errors were encountered:
Hi @ionic-team,
we're facing the same Bug in a Project with conditionally rendered slots, after we updated to ios18/macOS15: After an element renders a conditionally slot element, other slot elements on the same page gets removed.
This only seems to occur with elements whose slots have display: contents and contain text nodes. If you set the slot to e.g. display: block or wrap the text in an element such as span, p or div, the error does not occur.
In his example that would mean using <my-headline><span>Headline</span></my-headline> in my-app.ts would work.
Is it one of your short-term plans to review the incident?
At OutSystems we have limited resources and rely on contributions from the outside. If you are impacted by this problem, the best thing would be to get involved and help resolve it. This is not an "incident", I see this as a bug in an open source project that can be resolved by anyone who is impacted by it.
Prerequisites
Stencil Version
Tested with 2.22.3 and 4.22.2
Current Behavior
Elements are being "slotted" incorrectly into components with 'shadow:false' when added at runtime (with Angular's @if, for example).
Elements are inserted into default slot if it exists and as a first child of component if it does not.
Components with 'shadow:true' function as expected.
Expected Behavior
Elements are "slotted" into correct location (same as when using component with
shadow: true
)System Info
No response
Steps to Reproduce
Clone the repo
https://github.com/raqushque/stencil-ng-slots-repro
npm i --legacy-peer-deps
npm run start
In app click the buttons
Toggle content
orPush to array
. These add content that should be slotted.Code Reproduction URL
https://github.com/raqushque/stencil-ng-slots-repro
Additional Information
This is likely not a Stencil issue, but rather some sort of conflict between Stencil and Angular. Still, since
@stencil/angular-output-target
exists I'd expect component to work properly in both shadow and non-shadow modes, or this issue be documented. Also, default slots do work, so there could be a solution/workaround on Stencil's side.The text was updated successfully, but these errors were encountered: