New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable binding to CSS selectors #13886
Comments
Removed Type-En label. |
@pete, file bug here? |
I have some code sitting around that does almost exactly this. It's not integrated into polymer expressions, it just returns streams of elements that enter and exit the query. WIth the streams support in expressions, it might already work. I'll try it out. |
Added this to the Later milestone. |
Removed Area-Polymer label. |
Removed Library-PolymerExpressions label. |
Removed this from the 1.6 milestone. |
Added Polymer-P-2 label. |
Removed this from the Later milestone. |
Removed Polymer-P-2 label. |
Removed Polymer-Milestone-Later label. |
This issue has been moved to dart-archive/polymer-dart#482. |
I see a pattern in polymer.js of:
<foo-model id='foo'></foo-model>
<foo-consumer modelID='foo'></foo-consumer>
Where foo-consumer then resolves '#foo' in the document.
Would be much nicer if the following syntax could be used:
<foo-consumer model='{{$(#foo)}}'></foo-consumer>
And foo-consumer would get change events if that query selector happened to change.
The benefit of this is that foo-consumer can get it's model any way- via bindings, something programmatically setting it, or looking it up in the DOM.
The text was updated successfully, but these errors were encountered: