More advanced selector magic

[stuartpb]

Stuff I'm thinking about:

• [prop='val'] attribute syntax, maybe even with loosened quoting rules
• Allowing spaces (maybe with angle brackets) in selectors to create nested elements

[stuartpb]

Thinking about this a little bit: if you're creating a "nested element":

• Which element do you apply opts to?
• Which element do you return?

Seeing as how my gut answer for the first question is "the last one" and the last question is "the first one", I think these considerations are lopsided enough that I'd leave nested-element creation to nested cre calls.

[stuartpb]

As for prop="val"... I don't know that I want opts and the initial string to both be able to set props (ie. which one takes precedence in a conflict?) But I could maybe be persuaded if a compelling-enough case (ie. more compelling than, say, a ternary operator that switches property values in the initial element selector string) were suggested.