-
Notifications
You must be signed in to change notification settings - Fork 266
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
[0.6] textarea value bindings only work on stringInsert and stringRemove events #397
Comments
I have implemented a fix here: derbyjs/saddle#11 Not sure if it's the desired way to implement the fix, but my fix helps to show the issue as well. |
Bindings are implemented in Derby and not saddle. Was a bit more to this change also, since it needed OT of selection state as well. Fixed in: 89fcd2c |
Merged
minicuper
pushed a commit
that referenced
this issue
Jun 2, 2014
Fix textarea bug - #397 Nate, feel free to refactor the fix, if you wish :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This seems to be because the binding is a NodeBinding inside the textarea.
stringInsert and stringRemove textarea changes work because they directly set the .value property of a textarea.
On full value changes (instead of just stringInsert/stringRemove) the textarea's child node is indeed updated, but it is not reflected on the page as only directly setting .value of a textarea works.
The text was updated successfully, but these errors were encountered: