-
Notifications
You must be signed in to change notification settings - Fork 12
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
Why is content
not a property an requires attribute style binding $=
?
#18
Comments
Good point @lbustelo, thanks! |
Hopefully it could benefit in performance with Polymer 1.x, the question is how it applies to Polymer 2.0 Template binding. |
It seems, that there is a bug, which make this one required to work, as @warpech, @miyconst, @lbustelo, @deadlyfingers any ideas? I'd like to keep it short, meaningful and similar/related to |
in non-code-intrusive way, to make it work with Polymer 2.0-preview - workaround `$=` bug /issues/18 Polymer/polymer/issues/4060
(work in progress is available at |
My proposition for the new name is
WIP: https://github.com/Juicy/juicy-html/compare/issues/18-href-attr?expand=1 |
@warpech Maybe we should do it otherwise. Instead of facing dilemma whether to have attribute name that matches inline content and hyper link, and maintain hidden heuristic rules that guesses that you want to load external content. Just make it explicitly separated?
|
make `content` attr an alias to href tests for chenging proeprty are missing. #18
The above was agreed between me and @tomalec on Hangouts. |
@lbustelo Sorry, that it took that long. |
Would be nice if
content
could be set using property binding in adom-bind
template. Right now it requires$=
. At the very least, the README needs to reflect that requirement.The text was updated successfully, but these errors were encountered: