-
Notifications
You must be signed in to change notification settings - Fork 15
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
Include value along with change event #9
Comments
We should probably properly rewrite this library once improved-base is out. |
That's what I've already done, and I've added lot of stuff in the process (rendering manager, components, utilities for standard elements and events) :) but the code is still rather new and some things don't quite work properly yet or are incomplete I think you would normally access the value through the If the above is correct, I don't think the value should really be passed in as an argument, but there should at least be some API to retrieve it. |
This would require some means of reading an attribute (specifically |
This sounds correct, but it's worth noting that the target will be a DOM element and not a VNode, which is a good thing as I'm not sure you can extract the updated value from a VNode. Is there a reason the commented-out |
The current improved-base HEAD provides the
change
attribute which takes an action to run in the event of a change to a form element. There is however no way to actually access the value of the form element. Ideally the value changed to should be provided to thechange
handler.The text was updated successfully, but these errors were encountered: