Angular2/4 Forms Model doesn-t get properly updated on element.clear()
See original GitHub issueHi there!
It looks like there is a synchronization problem with Angular2(4) Forms when clearing an input field with element.clear().
A detailed description of the issue can be found here.
Best
Bug Report
- Node Version:
v7.8.0
- Protractor Version:
5.1.0
- Angular Version:
4.0.0
- Browser(s):
Chrome
- Operating System and Version
Ubuntu 16.10 LTS
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5
Top Results From Across the Web
Angular 2 - View not updating after model changes
It might be that the code in your service somehow breaks out of Angular's zone. This breaks change detection. This should work:
Read more >Angular 9 Update Guide | Brian F Love
Learn from a Google Developer Expert: Learn to successfully update to Angular version 9.
Read more >chsakell's Blog | Page 6 - chsakell's Blog
Add a new class library project named WcfProxies.Data in the solution and create a folder named Entities inside it. We 'll try to...
Read more >Bugs & Issues v4.2.X #807 | Support Center - ABP Commercial
After registering, I update again and delete the max min fields. rsm3.jpg. After click save button,ı get an error. resim4.jpg. How to create...
Read more >Christos S. – chsakell's Blog - RSSing.com
Model. Install Entity Framework using the Nuget Package Manager. ... private static List<Gadget> GetGadgets() { return new List<Gadget> { new Gadget { Name ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A similar problem existed ~4 years ago.
The workaround https://github.com/angular/protractor/issues/301#issuecomment-32651201 fixed it for me also on angular 5 / protractor 5.2.0.
This has been fixed and we also have tests for it, see https://github.com/angular/protractor/commit/b93c8310f8aaccbebed672eeb42e156d47d16f0a