Re: [webcomponents] When is the slotting algorithm run (#401)

I added dfn.js to the spec. It looks that the (reverse) dependency is:

```
"slotting algorithm": http://w3c.github.io/webcomponents/spec/shadow/#dfn-slotting-algorithm
  ->  "assigned slot": http://w3c.github.io/webcomponents/spec/shadow/#dfn-assigned-slot
    ->  "assigned": http://w3c.github.io/webcomponents/spec/shadow/#dfn-assigned
      ->  "get assigned nodes algorithm": http://w3c.github.io/webcomponents/spec/shadow/#dfn-get-assigned-nodes-algorithm
        ->  "assigned nodes": http://w3c.github.io/webcomponents/spec/shadow/#dfn-assigned-nodes
          -> "distributed nodes algorithm": http://w3c.github.io/webcomponents/spec/shadow/#distributed-nodes-algorithm
            -> "distributed nodes" for a slot: http://w3c.github.io/webcomponents/spec/shadow/#dfn-distributed-nodes
              -> "flattening algorithm": http://w3c.github.io/webcomponents/spec/shadow/#dfn-distributed-nodes
                -> "flat tree": http://w3c.github.io/webcomponents/spec/shadow/#dfn-flat-tree
                   -> In resolving CSS inheritance, an element must inherit from the parent node in the flat tree, if applicable.
                   -> .. others
              -> "getAssignedNodes" method
        -> "getAssignedNodes" method
```

Thus, the consumers are getAssignedNodes() and (how to construct) a flat tree. 

> It seems easier to specify this as a lazy algorithm if this is only used for assignedSlot and getAssignedNodes().

Yes, that's my intention. I thought that we can keep the spec simple by this laziness (declarative) definition. I would like to avoid to specify the timing when these algorithm are run.



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