"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/content/guide/migration.ngdoc" between
angular.js-1.7.9.tar.gz and angular.js-1.8.0.tar.gz

About: AngularJS is a web application framework that assists with creating single-page applications that only require HTML, CSS, and JavaScript on the client side.

migration.ngdoc  (angular.js-1.7.9):migration.ngdoc  (angular.js-1.8.0)
skipping to change at line 18 skipping to change at line 18
Minor version releases in AngularJS introduce several breaking changes that may require changes to your Minor version releases in AngularJS introduce several breaking changes that may require changes to your
application's source code; for instance from 1.0 to 1.2 and from 1.2 to 1.3. application's source code; for instance from 1.0 to 1.2 and from 1.2 to 1.3.
Although we try to avoid breaking changes, there are some cases where it is unav oidable: Although we try to avoid breaking changes, there are some cases where it is unav oidable:
* AngularJS has undergone thorough security reviews to make applications safer b y default, * AngularJS has undergone thorough security reviews to make applications safer b y default,
which drives many of these changes. which drives many of these changes.
* Several new features, especially animations, would not be possible without a f ew changes. * Several new features, especially animations, would not be possible without a f ew changes.
* Finally, some outstanding bugs were best fixed by changing an existing API. * Finally, some outstanding bugs were best fixed by changing an existing API.
## Migrating from 1.7 to 1.8
Generally updating to 1.8.0 from 1.7.x should be a straightforward process and i
s highly recommended.
AngularJS 1.8 is a breaking change release from 1.7 to mitigate a security issue
.
JqLite no longer turns XHTML-like strings like `<div /><span />` to sibling elem
ents when not in XHTML
mode: `<div></div><span></span>`.
Instead it will leave the elements alone. In non-XHTML mode the browser will con
vert these to nested
elements: `<div><span></span></div>`.
This is a security fix to avoid an XSS vulnerability if a new jqLite element is
created from a
user-controlled HTML string. If you must have this functionality and understand
the risk involved
then it is posible to restore the original behavior by calling
```js
angular.UNSAFE_restoreLegacyJqLiteXHTMLReplacement();
```
But you should adjust your code for this change and remove your use of this func
tion as soon as
possible.
Note that this only patches jqLite. If you use jQuery 3.5.0 or newer, please rea
d the
[jQuery 3.5 upgrade guide](https://jquery.com/upgrade-guide/3.5/) for more detai
ls about the workarounds.
## Migrating from 1.6 to 1.7 ## Migrating from 1.6 to 1.7
AngularJS 1.7 contains bug fixes and features to AngularJS core and its external modules, some of AngularJS 1.7 contains bug fixes and features to AngularJS core and its external modules, some of
which contain breaking changes. However, most of these address internal behavior and not APIs, and which contain breaking changes. However, most of these address internal behavior and not APIs, and
should not affect many applications. should not affect many applications.
Additionally, we have removed some long-deprecated modules and APIs. Additionally, we have removed some long-deprecated modules and APIs.
The most notable changes are: The most notable changes are:
- `$resource` has now support for request and requestError interceptors - `$resource` has now support for request and requestError interceptors
 End of changes. 1 change blocks. 
0 lines changed or deleted 33 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)