This was spurred by a conversation on polymer-dev. I think this is a little clearer, because we expect people to provide a child element that fires iron-select, but listening for that iron-select is probably one of the key ways to get the output of the element.
Although you can also bind to value, selectedItem, or selectedItemLabel, which I didn't mention. Hm... Well, anyway, it's a start.
Perhaps the example should show one of these things (for example, binding to value or selectedItemLabel) as well to make it more of a complete example?
cdata
commented
8 years ago
This was spurred by a conversation on polymer-dev. I think this is a little clearer, because we expect people to provide a child element that fires
iron-select, but listening for thatiron-selectis probably one of the key ways to get the output of the element.Although you can also bind to
value,selectedItem, orselectedItemLabel, which I didn't mention. Hm... Well, anyway, it's a start.Perhaps the example should show one of these things (for example, binding to
valueorselectedItemLabel) as well to make it more of a complete example?