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
The imperative Shadow DOM distribution API allows developers to explicitly set the assigned nodes for a slot element. With this API, web developers can create web components without needing to add specific markup, slot="" attribute, to children of host component. In addition, it enables conditional slotting based on either environmental state or an attribute passed in.
More details, including more motivating uses cases, can be found in the explainer.
The behavior of this API has been discussed in the last TPAC F2F back in Sept, 2019. The proposal has been implemented in Chrome and we would like to get an official stance from Mozzila.
I think the proposal looks reasonable and should be relatively easy to implement.
And when looking at w3ctag/design-reviews#486 (comment), I think it is even good that the proposal doesn't include too many new features at once. If some default slot mechanism is needed, it could be added later.
So I think this is worth prototyping.
Request for Mozilla Position on an Emerging Web Specification
Other information
The imperative Shadow DOM distribution API allows developers to explicitly set the assigned nodes for a slot element. With this API, web developers can create web components without needing to add specific markup, slot="" attribute, to children of host component. In addition, it enables conditional slotting based on either environmental state or an attribute passed in.
More details, including more motivating uses cases, can be found in the explainer.
The behavior of this API has been discussed in the last TPAC F2F back in Sept, 2019. The proposal has been implemented in Chrome and we would like to get an official stance from Mozzila.
Example syntax:
The text was updated successfully, but these errors were encountered: