I think we can learn something from existing programming languages.
For example, I like Python's way to handle function's parameters. That
enables us to select:
- By Position
- By Keyword
- *args (Grab unused positional arguments)
- *kwds* (Grap unused keyword arguments)
I think this is over-engineering for us. But this might be interesting to
us as a reference.
On Tue, May 19, 2015 at 12:54 PM Hayato Ito <hayato@chromium.org> wrote:
> I think the problem we have to solve is:
>
> Problem: "Given that we have a list of nodes, what's the best way to
> select nodes from the list? We can give any *hint* to the nodes beforehand
> if we wish."
>
> Is this a correct problem statement? I think we don't have to limit our
> answers to this problem by the current select and the content-slot.
> Any better ideas can be acceptable, I think.
>
> The hint we can use is:
>
> - tag name
> - id attribute
> - class attribute
> - any other attributes. (Okay to have a dedicated attribute, such as
> 'content-slot')
> - The position of the node in the list
> - Other status, such as ":focused" (in CSS's terminology)
> - Anything else?
>
> I think the current <content select> has been there in the spec for a
> long time. No one hasn't spent much time on thinking a replacement of it
> until recently.
> I hope that this discussion might be a good opportunity to get an
> agreement between us.
>
>
> On Tue, May 19, 2015 at 12:23 PM Dimitri Glazkov <dglazkov@google.com>
> wrote:
>
>> On Mon, May 18, 2015 at 8:18 PM, Hayato Ito <hayato@chromium.org> wrote:
>>>
>>> Thank you! I'm afraid that we don't have enough discussion about the
>>> pros and cons between "select nodes using a selector" and "select nodes by
>>> a fixed id using attribute".
>>>
>>
>> BTW, here's one bit of research I'd done:
>> https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Partial-Redistributions-Analysis.md
>>
>> :DG<
>>
>