angular.js/docs/content, branch v0.10.5 feat(docs): Add scenario runner into dev guide 2011-10-26T22:58:59+00:00 Vojta Jina 2011-10-25T20:23:49+00:00 bf729d550b9589aa498957d219816e334222858b And update the link in the tutorial as well... 
And update the link in the tutorial as well...
feat(bootstrap): drop angular.js file name restrictions for autobind 2011-10-26T19:57:15+00:00 Igor Minar 2011-10-25T15:47:02+00:00 d7ba5bc83ba9a8937384ea677331c5156ed6772d The last script element in the dom is always us if the script that contains angular is loaded synchronously. For async loading manual bootstrap needs to be performed. Close #621 
The last script element in the dom is always us if the script that
contains angular is loaded synchronously.

For async loading manual bootstrap needs to be performed.

Close #621
fix(compiler): revert 8611ebe6 - calling \$digest after linking 2011-10-20T22:51:14+00:00 Igor Minar 2011-10-20T22:37:37+00:00 f38010d3a2f457a53798212ef72418637dabe189 Change introduced by me in 8611ebe6 results in considerable inefficiencies when the compiler and linker is used from within a widget, in which case, we call $digest unnecessary since it will be called by the $apply which called the directive/widget in the first place. There are only two places when the extra $digest call can be useful - when manually bootstrapping the app or in tests. However even in tests this behavior can result in unwanted results (especially when ng:controller is involved). So it is better to leave it for the developer to call $digest when it is really needed. 
Change introduced by me in 8611ebe6 results in considerable inefficiencies when the compiler
and linker is used from within a widget, in which case, we call $digest unnecessary since it
will be called by the $apply which called the directive/widget in the first place.

There are only two places when the extra $digest call can be useful - when manually bootstrapping
the app or in tests. However even in tests this behavior can result in unwanted results (especially
when ng:controller is involved). So it is better to leave it for the developer to call $digest
when it is really needed.
docs(forms): fix devguide forms example code 2011-10-14T15:30:02+00:00 Igor Minar 2011-10-14T15:30:02+00:00 b0c3f28e8f541ccf6c25e3fdd3f3cae8c727e067 






docs(cookbook): disable jsfiddle for deeplinking example
2011-10-14T15:29:33+00:00

Igor Minar

2011-10-14T15:29:33+00:00

9810dc0993bbb6509b3b7f77abaf8fcfef1f45bf

it uses extra resources, so it won't work on fiddle





it uses extra resources, so it won't work on fiddle







docs($location): Html5 -> HTML5
2011-10-13T21:42:49+00:00

Igor Minar

2011-10-13T21:42:41+00:00

ad5e42cf8229a40d8dfd3f3e178207b2af1cdb14












docs($location): update replace() docs
2011-10-13T21:37:37+00:00

Igor Minar

2011-10-13T21:36:42+00:00

9ed1126adb56cbeebd23f3589decff2ac6bc36b3












docs($location): fix $config -> $locationConfig in docs
2011-10-13T21:07:48+00:00

Igor Minar

2011-10-13T21:07:35+00:00

7a19eb84aa3df39f42e42a4e4ac0b169862119be












docs(dev_guide.bootstrap.auto_bootstrap): fixing a typo
2011-10-13T06:04:48+00:00

Igor Minar

2011-10-13T05:50:35+00:00

28ccc76aa17f6107bea692ad4782cfb209e7a10f












docs(*): remove @workInProgress from everywhere
2011-10-13T06:04:48+00:00

Igor Minar

2011-10-12T19:19:39+00:00

b3c4cb7cff8bab6e0e3d7e68870ed6316bbd5241

it's not useful any more and it only makes the docs look ugly





it's not useful any more and it only makes the docs look ugly