Closed b-hobbs closed 6 years ago
Same problem.
I provided a solution in SO for this and then found this open defect. Please fix this within the ng2-idle. Thx @b-hobbs for opening this issue.
still experiencing this issue, any solutions yet?
Any updates on this issue?
Closed via #74
i have same problem with version 7.0.0-beta.1
I'm submitting a ... (check one with "x")
Current behavior
ng2-idle's watching uses setInterval on the main angular zone which is blocking Protractor because it waits until all calls in the main zone are finished.
Expected behavior
setInterval is run outside of the main angular zone so that it doesn't block Protractor.
Minimal reproduction of the problem with instructions
You should be able to add protractor to an app setup for ng2-idle and use
protractor --elementExplorer
and try to grab an element through Protractor's api.Workaround Should preferably deal with this inside of the plugin itself.
What is the motivation / use case for changing the behavior?
Protractor tests don't work
Please tell us about your environment:
OSX EL Capitan 10.11.6 VS Code
@ng-idle version: 2.x
2.0.0-beta.4
Angular version: 2.x
2.4.7
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
ALL
Language: [all | TypeScript X.X | ES6/7 | ES5] ALL
Node:
node --version
= 7