Re: [webcomponents] Remove the constraint that slot can't have another slot as an ancestor (#321)

Right. The motivation is to avoid the unnecessary validation in engines as well as making the behavior of slots more consistent.

I don't think we should merge the issues.  #317 is about enabling fallback contents, this issue is about not having this constraint.

It's true that removing this constraint doesn't allow new use cases without allowing fallback contents for slots, it still makes the behaviors of slot elements simpler and more consistent.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/321#issuecomment-141043623