Skip to content
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

ngHandsontable - Cell edit causes ng-model issue #161

Closed
murph1329 opened this issue May 31, 2016 · 3 comments
Closed

ngHandsontable - Cell edit causes ng-model issue #161

murph1329 opened this issue May 31, 2016 · 3 comments

Comments

@murph1329
Copy link

murph1329 commented May 31, 2016

This is a duplicate issue of one posted on the handsontable forum. I'm including it here as well to see if the community has a work around.

Original Posting:
https://forum.handsontable.com/t/nghandsontable-cell-edit-causes-ng-model-issue/379/1

Details:
Browser: IE11
AngularJS: v1.4.10
ngHandsontable: 0.12.0

I'm only able to duplicate the following issue using IE11, Chrome works fine.

JSBin Sample:
http://jsbin.com/mutotikuke/edit?html,js,output

Steps to reproduce:
Edit any cell in "ID" column (do not press enter or any table navigation key)
After edit immediately click on "filter" textbox
Type text into "filter" textbox

EXPECTED RESULT: {{ctrl.filter}} should correspond to item in "filter" textbox
DEFECT: model is not updated

This is a critical issue to us as it could lead to data loss.

Thanks,
Wes

@murph1329
Copy link
Author

@murph1329
Copy link
Author

murph1329 commented Jun 11, 2016

UPDATE:

I've added a comment to the following ticket over at the AngularJS github site. Honestly I'm not really happy about the feedback I'm seeing.
angular/angular.js#11193

I'm not sure if there is anything the handsontable team can do about this issue but I really want to see that everyone is made aware of it as I believe it has the potential to be catastrophic due to the ease of data loss.

If anyone has a work around for it, even if it is a hackish type of approach, please share it with the community so we can be made aware of it.

Thanks,
Wes

@AMBudnik
Copy link

AMBudnik commented Mar 6, 2018

Sorry that there was no reply for a longer time.
I am sure that you have already finished the project or abandoned it so I am closing the issue. However if not I'll reopen the issue.

@AMBudnik AMBudnik closed this as completed Mar 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants