|
| 1 | +<a name="1.3.0-beta.10"></a> |
| 2 | +# 1.3.0-beta.10 excessive-clarification (2014-05-23) |
| 3 | + |
| 4 | + |
| 5 | +## Bug Fixes |
| 6 | + |
| 7 | +- **$animate:** retain inline styles for property-specific transitions |
| 8 | + ([98b9d68e](https://github.com/angular/angular.js/commit/98b9d68ea3ecfb521e9279c9cbfe93f8ba7d626e), |
| 9 | + [#7503](https://github.com/angular/angular.js/issues/7503)) |
| 10 | +- **$compile:** do not merge attrs that are the same for replace directives |
| 11 | + ([1ab6e908](https://github.com/angular/angular.js/commit/1ab6e908b15470d59b52eb0ead20c755c66ec3b8), |
| 12 | + [#7463](https://github.com/angular/angular.js/issues/7463)) |
| 13 | +- **$parse:** remove deprecated promise unwrapping |
| 14 | + ([fa6e411d](https://github.com/angular/angular.js/commit/fa6e411da26824a5bae55f37ce7dbb859653276d)) |
| 15 | +- **Scope:** $broadcast and $emit should set event.currentScope to null |
| 16 | + ([82f45aee](https://github.com/angular/angular.js/commit/82f45aee5bd84d1cc53fb2e8f645d2263cdaacbc), |
| 17 | + [#7445](https://github.com/angular/angular.js/issues/7445), [#7523](https://github.com/angular/angular.js/issues/7523)) |
| 18 | +- **ngModel:** do not dirty the input on $commitViewValue if nothing was changed |
| 19 | + ([facd904a](https://github.com/angular/angular.js/commit/facd904a613e716151a13ab7460b5e6206e0442b), |
| 20 | + [#7457](https://github.com/angular/angular.js/issues/7457), [#7495](https://github.com/angular/angular.js/issues/7495)) |
| 21 | + |
| 22 | + |
| 23 | +## Features |
| 24 | + |
| 25 | +- **$interpolate:** escaped interpolation expressions |
| 26 | + ([e3f78c17](https://github.com/angular/angular.js/commit/e3f78c17d3b5d3a714402d7314094aabe7f6512a), |
| 27 | + [#5601](https://github.com/angular/angular.js/issues/5601), [#7517](https://github.com/angular/angular.js/issues/7517)) |
| 28 | +- **{{ bindings }}:** lazy one-time binding support |
| 29 | + ([cee429f0](https://github.com/angular/angular.js/commit/cee429f0aaebf32ef1c9aedd8447a48f163dd0a4), |
| 30 | + [#7486](https://github.com/angular/angular.js/issues/7486), [#5408](https://github.com/angular/angular.js/issues/5408)) |
| 31 | +- **ngMock:** add support of mocha tdd interface |
| 32 | + ([854bf5b7](https://github.com/angular/angular.js/commit/854bf5b74d0395f4d2e30382102d3f5d1614ea11), |
| 33 | + [#7489](https://github.com/angular/angular.js/issues/7489)) |
| 34 | + |
| 35 | + |
| 36 | +## Performance Improvements |
| 37 | + |
| 38 | +- **$interpolate:** optimize value stringification |
| 39 | + ([e927193d](https://github.com/angular/angular.js/commit/e927193de06500f01a2f893934250911cf1905e6), |
| 40 | + [#7501](https://github.com/angular/angular.js/issues/7501)) |
| 41 | + |
| 42 | + |
| 43 | +## Breaking Changes |
| 44 | + |
| 45 | +- **$compile:** due to [eec6394a](https://github.com/angular/angular.js/commit/eec6394a342fb92fba5270eee11c83f1d895e9fb), The `replace` flag for defining directives that |
| 46 | + replace the element that they are on will be removed in the next major angular version. |
| 47 | + This feature has difficult semantics (e.g. how attributes are merged) and leads to more |
| 48 | + problems compared to what it solves. Also, with Web Components it is normal to have |
| 49 | + custom elements in the DOM. |
| 50 | + |
| 51 | +- **$parse:** due to [fa6e411d](https://github.com/angular/angular.js/commit/fa6e411da26824a5bae55f37ce7dbb859653276d), |
| 52 | + promise unwrapping has been removed. It has been deprecated since 1.2.0-rc.3. |
| 53 | + It can no longer be turned on. |
| 54 | + Two methods have been removed: |
| 55 | + * `$parseProvider.unwrapPromises` |
| 56 | + * `$parseProvider.logPromiseWarnings` |
| 57 | + |
| 58 | +- **Scope:** due to [82f45aee](https://github.com/angular/angular.js/commit/82f45aee5bd84d1cc53fb2e8f645d2263cdaacbc), |
| 59 | + [#7445](https://github.com/angular/angular.js/issues/7445), |
| 60 | + [#7523](https://github.com/angular/angular.js/issues/7523) |
| 61 | + `$broadcast` and `$emit` will now reset the `currentScope` property of the event to |
| 62 | + null once the event finished propagating. If any code depends on asynchronously accessing their |
| 63 | + `currentScope` property, it should be migrated to use `targetScope` instead. All of these cases |
| 64 | + should be considered programming bugs. |
| 65 | + |
| 66 | + |
1 | 67 | <a name="1.3.0-beta.9"></a>
|
2 | 68 | # 1.3.0-beta.9 release-naming (2014-05-16)
|
3 | 69 |
|
|
0 commit comments