-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
setting value option on <option> tags #178
Labels
Comments
Huh, another fascinating quirk of the DOM: if you do |
Interesting find. Thanks for your quick reply. 👍
…On 12/12/2016 8:12 AM, "Rich Harris" ***@***.***> wrote:
Huh, another fascinating quirk of the DOM: if you do input.setAttribute('list',
'suggestions'), it works, but not if you do input.list = 'suggestions'.
If you do the latter, the list property has to be the <datalist> element
itself, not the ID.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#178 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIiaJKLNWGSfzhGyet4hJXlcD9TzwqOqks5rHEslgaJpZM4LJzJ0>
.
|
Rich-Harris
added a commit
that referenced
this issue
Dec 12, 2016
use setAttribute() for list attributes
Released 1.2.3 with the fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that you can not dynamically generation tags with dynamically defined values.
Have created a REPL here: https://svelte.technology/repl/?gist=31068d1476982e9e6deac89e097bb018
The text was updated successfully, but these errors were encountered: