GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2312
ZEPPELIN-2486. AngularElem's onChange is only invoked once
### What is this PR for?
`ng-change` can not capture event, so that means `$event.timeStamp` is
undefined. https://github.com/angular/angular.js/issues/6370
This cause AngularElem's onChange is only invoked once.
### What type of PR is it?
[Bug Fix]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2486
### How should this be tested?
Tested manually
### Screenshots (if appropriate)
Before
After
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2486
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2312.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2312
----
commit 4cbb1a1cbf870b7e838efa23943c7a8ef6c28b34
Author: Jeff Zhang <[email protected]>
Date: 2017-05-03T12:42:34Z
ZEPPELIN-2486. ng-change is only invoked once for AngularElem
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
