Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504)

I do not see any clear reason why we need distributedCallback.
The problem which `distributedCallback` solves looks non-essential to me. Rather, that sounds *opposite of interests*. It is anti-pattern, isn't it?

e.g.
Suppose `<summary>` and `<details>` elements.
- `<summary>` element does not throw any exception nor emit any warnings even if it is used outside of `<details>` element.
- `<summary>` element should not have such an initiative. Rather, it's `<details>` element's responsibility to coordinate with `<summary>`. `<details>` should take care of `<summary>`, but the opposite is not true.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/504#issuecomment-231648240