Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308)

> It would be problematic if they are projected inside the `<slot>`. In that case one couldn't, for example, project elements into an element that has `display: flex`.

> ```
 <x-b>
  SR
    <div style="display: flex;"><slot></slot></div>
  <div>flex item?</div>
```

I see.  That's a pretty good argument for keeping the currently spec'ed behavior although it feels like we're working around the limitation of CSS.

If we had a new display type like `display: ignore` which replaces a node with its children for the purpose of box generations, we wouldn't need to do this, right?

One thing I don't like about the current model is the discrepancy between the composed tree as exposed to CSS and the tree event dispatching takes place.  Namely, the event path will include the slot element that is a deep ancestor of the target.

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