angularjs-ng-change

So I have a select tag that shows some options and I wish that when an option is selected it takes the data-something attribute and pastes its value (of the attribute) in the input element I have. It is only demonstrative, value attribute should be send in the form. <input ng-model="refreshedByExample" type="text"> <select ng-model="example"> <option value="1" data-something="valueForRefreshedByExample1">1</option> <option value="2" data-something="valueForRefreshedByExample2">2</option> <option value="3" data-something="valueForRefreshedByExample3">3</option> </select> Any ideas? Thanks a lot

I have an instance where I'm replacing the value of ngModel through ngChange . The cursor jumps to the end of the input field after each change (assuming because I'm assigning the result to the same $scope variable.) I'd like to know how I can prevent this behavior? $scope.compute1 = 0; $scope.compute2 = 10; $scope.math = function() { $scope.compute1 = parseInt($scope.compute1); $scope.compute2 = parseInt($scope.compute2); $scope.compute1 = parseInt($scope.compute1); }; fiddle Example of problem: if a user types in 1000. It's fine. But then if they want to go back and change the number to

//main controller angular.module('myApp') .controller('mainCtrl', function ($scope){ $scope.loadResults = function (){ console.log($scope.searchFilter); }; }); // directive angular.module('myApp') .directive('customSearch', function () { return { scope: { searchModel: '=ngModel', searchChange: '&ngChange', }, require: 'ngModel', template: '<input type="text" ng-model="searchModel" ng-change="searchChange()"/>', restrict: 'E' }; }); // html <custom-search ng-model="searchFilter" ng-change="loadResults()"></custom-search> Here is a simplified directive to illustrate. When I type into the input,

When should I use angular $watch functions and when use ng-change angularjs directive? To me, they both can do the same. Are there any differences or usage patterns between them? They are not the same, clearly. One is used solely in the controller; the other is a directive on an input element. But even in their application they differ. When you use $watch the watched expression will be evaluated on every digest cycle, and if there is a change, the handler is invoked. With ng-change , the handler is invoked explicitly in response to an event. With $watch , change can come from anywhere: user

I have an input field, where I want to apply the variant of ngChange . The input field is sort of binding with an ajax call, when user changes the input, the server side will process the data, however, I don't wanna make the call too often. Say the user wanna input a really string, I want the call be made only after user finishes the word he is about to type. Nevertheless, I don't wanna use event such as blur. What would be a better way to implement this, rather than setTimeout ? Use ng-model-options in Angular > 1.3 <input type="text" ng-model="vm.searchTerm" ng-change="vm.search(vm

Angular ng-change on ng-model passed into child directive Basically, I want to be able to pass in ng-model from a parent directive to a child directive. I could just in a 2-way binded value, but then I wouldn't be able to use a ng-change in the parent directive on the child element. I could also use ng-click, but this wouldn't work with a non-clicking change (such as a text area instead of a checkbox). So I'm wondering if there's a way to allow a custom directives to have a ng-model/ng-change pair similar to how inputs, buttons, text areas and other html elements can. I want to avoid using

I'm working on an edit form (user.html) that PUTs data to an API, but I'd like to avoid PUTting all the data in the form. I'd like to PUT just the changed items. I've seen the use of dirty and pristine when working with forms, but this applies to any change in the form. I've also seen the use of ng-change, but I don't want to trigger an action on a change to one element, just denote that the changed element should be included in the PUT. Anyone found a way to denote only the input fields that have changed? If you put the input in a form with a name attribute and then give the input a name

I have a directive with a template like <div> <div ng-repeat="item in items" ng-click="updateModel(item)"> <div> My directive is declared as: return { templateUrl: '...', restrict: 'E', require: '^ngModel', scope: { items: '=', ngModel: '=', ngChange: '&' }, link: function postLink(scope, element, attrs) { scope.updateModel = function(item) { scope.ngModel = item; scope.ngChange(); } } } I would like to have ng-change called when an item is clicked and the value of foo has been changed already. That is, if my directive is implemented as: <my-directive items=items ng-model="foo" ng-change="bar