angular.js -

Age	Commit message (Collapse)	Author
2012-04-09	fix(ngBindHtml): clear contents when model is falsy	Igor Minar
	Closes #864
2012-04-09	fix(docs): change all directive references to use the normalized names	Igor Minar

2012-04-04	fix(docs): remove ngModelInstant from all examples	Igor Minar
	just fixing leftover code after the removal of ngModelInstant
2012-04-04	chore(directive): correct file names for booleanAttrs	Vojta Jina

2012-04-04	fix(booleanAttrs): convert to boolean	Vojta Jina
	jQuery's attr() does not handle 0 as false, when it comes to boolean attrs.
2012-04-03	fix(form): preperly clean up when invalid widget is removed	Misko Hevery
	Removing invalid widget sometimes resulted in improper cleanup of the form state.
2012-04-03	fix(ng-href): copy even if no binding	Misko Hevery
	Closes# 850 fixed an issue where ng-href would not copy its content into href if it did not contain binding.
2012-04-03	refactor(ngView): remove extra $watch, refactor one ugly test	Vojta Jina

2012-04-03	feat(ngInclude): allow ngInclude on css class	Vojta Jina
	And make it terminal so that it does not compile its content, which would cause leaks.
2012-04-03	fix(ngInclude): fire $includeContentLoaded on proper (child) scope	Vojta Jina

2012-04-03	refactor(ngInclude): remove scope attribute	Vojta Jina
	The purpose of allowing the scope to be specified was to enable the $route service to work together with ngInclude. However the functionality of creating scopes was in the recent past moved from the $route service to the ngView directive, so currently there is no valid use case for specifying the scope for ngInclude. In fact, allowing the scope to be defined can under certain circumstances lead to memory leaks. Breaks ngInclude does not have scope attribute anymore.
2012-04-03	feat(ngModel): update model on each key stroke (revert ngModelInstant)	Vojta Jina
	It turns out that listening only on "blur" event is not sufficient in many scenarios, especially when you use form validation you always had to use ngModelnstant e.g. if you want to disable a button based on valid/invalid form. The feedback we got from our apps as well as external apps is that the ngModelInstant should be the default. In the future we might provide alternative ways of suppressing updates on each key stroke, but it's not going to be the default behavior. Apps already using the ngModelInstant can safely remove it from their templates. Input fields without ngModelInstant directive will start propagating the input changes into the model on each key stroke.
2012-03-29	fix(FormController): ask for dependency to fool the BC module	Igor Minar

2012-03-29	fix(ngValue): bind properly inside ng-repeat	Vojta Jina

2012-03-29	refactor($compile): move methods of attr object into prototype	Vojta Jina
	We have many instances of this object and we clone them as well (e.g. ng-repeat). This should save some memory and performance as well. Double prefixed private properties of attr object: attr.$element -> attr.$$element attr.$observers -> attr.$$observers Update shallowCopy to not copy $$ properties and allow passing optional destination object.
2012-03-29	fix($compile): properly clone attr.$observers in ng-repeat	Vojta Jina
	The `attr` object was only shallow copied which caused all observers to be shared. Fixing similar issue in ng-* boolean attributes as well as ng-src and ng-href.
2012-03-28	refactor(toJson): use native JSON.stringify	Igor Minar
	Instead of using our custom serializer we now use the native one and use the replacer function to customize the serialization to preserve most of the previous behavior (ignore $ and $$ properties as well as window, document and scope instances).
2012-03-28	chore(module): move files around in preparation for more modules	Misko Hevery