angular-1.8.0.zip

<a href='https://github.com/angular/angular.js/edit/v1.8.x/docs/content/guide/migration.ngdoc?message=docs(guide%2FMigrating from Previous Versions)%3A%20describe%20your%20change...' class='improve-docs btn btn-primary'><i class="glyphicon glyphicon-edit">&nbsp;</i>Improve this Doc</a> <h1 id="migrating-an-app-to-a-newer-version">Migrating an App to a newer version</h1> <p>Minor version releases in AngularJS introduce several breaking changes that may require changes to your application&#39;s source code; for instance from 1.0 to 1.2 and from 1.2 to 1.3.</p> <p>Although we try to avoid breaking changes, there are some cases where it is unavoidable:</p> <ul> <li>AngularJS has undergone thorough security reviews to make applications safer by default, which drives many of these changes.</li> <li>Several new features, especially animations, would not be possible without a few changes.</li> <li>Finally, some outstanding bugs were best fixed by changing an existing API.</li> </ul> <h2 id="migrating-from-1-7-to-1-8">Migrating from 1.7 to 1.8</h2> <p>Generally updating to 1.8.0 from 1.7.x should be a straightforward process and is highly recommended. AngularJS 1.8 is a breaking change release from 1.7 to mitigate a security issue.</p> <p>JqLite no longer turns XHTML-like strings like <code>&lt;div /&gt;&lt;span /&gt;</code> to sibling elements when not in XHTML mode: <code>&lt;div&gt;&lt;/div&gt;&lt;span&gt;&lt;/span&gt;</code>. Instead it will leave the elements alone. In non-XHTML mode the browser will convert these to nested elements: <code>&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;</code>.</p> <p>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</p> <pre><code class="lang-js">angular.UNSAFE_restoreLegacyJqLiteXHTMLReplacement(); </code></pre> <p>But you should adjust your code for this change and remove your use of this function as soon as possible.</p> <p>Note that this only patches jqLite. If you use jQuery 3.5.0 or newer, please read the <a href="https://jquery.com/upgrade-guide/3.5/">jQuery 3.5 upgrade guide</a> for more details about the workarounds.</p> <h2 id="migrating-from-1-6-to-1-7">Migrating from 1.6 to 1.7</h2> <p>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 should not affect many applications. Additionally, we have removed some long-deprecated modules and APIs.</p> <p>The most notable changes are:</p> <ul> <li><p><code>$resource</code> has now support for request and requestError interceptors</p> </li> <li><p>Several deprecated features have been removed:</p> <ul> <li>the <code>$controllerProvider.allowGlobals()</code> flag</li> <li>the <code>$compileProvider.preAssignBindingsEnabled()</code> flag</li> <li>the <code>angular.lowercase</code> and <code>angular.uppercase</code> methods</li> <li>the <code>$cookieStore</code> service from the <code>ngCookies</code> module</li> <li>the <code>ngClick</code> override directive and corresponding services from the <code>ngTouch</code> module</li> <li>the complete <code>ngScenario</code> module</li> </ul> </li> </ul> <p>Please note that feature development (without breaking changes) has happened in parallel on the 1.6.x branch, so 1.7 doesn&#39;t contain many new features, but you may still benefit from those features that were added (with possible BCs), bugfixes, and a few smaller performance improvements.</p> <p><br /> Below is the full list of breaking changes:</p> <p><br /> <a name="migrate1.6to1.7-ng-directives"></a></p> <h3 id="core-_directives_">Core: <em>Directives</em></h3> <h4 id="-form-"><strong>form</strong></h4> <p><strong>Due to <a href="https://github.com/angular/angular.js/commit/223de59e988dc0cc8b4ec3a045b7c0735eba1c77">223de5</a></strong>, forms will now set <code>$submitted</code> on child forms when they are submitted. For example:</p> <pre><code>&lt;form name=&quot;parentform&quot; ng-submit=&quot;$ctrl.submit()&quot;&gt; &lt;ng-form name=&quot;childform&quot;&gt; &lt;input type=&quot;text&quot; name=&quot;input&quot; ng-model=&quot;my.model&quot; /&gt; &lt;/ng-form&gt; &lt;input type=&quot;submit&quot; /&gt; &lt;/form&gt; </code></pre> <p>Submitting this form will set <code>$submitted</code> on &quot;parentform&quot; and &quot;childform&quot;. Previously, it was only set on &quot;parentform&quot;.</p> <p>This change was introduced because mixing <code>form</code> and <code>ngForm</code> does not create logically separate forms, but rather something like input groups. Therefore, child forms should inherit the submission state from their parent form.</p> <h4 id="-input-radio-and-input-checkbox-"><strong>input[radio]</strong> and <strong>input[checkbox]</strong></h4> <p><strong>Due to <a href="https://github.com/angular/angular.js/commit/656c8fa8f23b1277cc5c214c4d0237f3393afa1e">656c8f</a></strong>, <code>input[radio]</code> and <code>input[checkbox]</code> now listen to the &quot;change&quot; event instead of the &quot;click&quot; event. Most apps should not be affected, as &quot;change&quot; is automatically fired by browsers after &quot;click&quot; happens.</p> <p>Two scenarios might need migration:</p> <ul> <li>Custom click events:</li> </ul> <p>Before this change, custom click event listeners on radio / checkbox would be called after the input element and <code>ngModel</code> had been updated, unless they were specifically registered before the built-in click handlers. After this change, they are called before the input is updated, and can call <code>event.preventDefault()</code> to prevent the input from updating.</p> <p>If an app uses a click event listener that expects <code>ngModel</code> to be updated when it is called, it now needs to register a change event listener instead.</p> <ul> <li>Triggering click events:</li> </ul> <p>Conventional trigger functions:</p> <p>The change event might not be fired when the input element is not attached to the document. This can happen in <strong>tests</strong> that compile input elements and trigger click events on them. Depending on the browser (Chrome and Safari) and the trigger method, the change event will not be fired when the input isn&#39;t attached to the document.</p> <p>Before:</p> <pre><code class="lang-js">it(&#39;should update the model&#39;, inject(function($compile, $rootScope) { var inputElm = $compile(&#39;&lt;input type=&quot;checkbox&quot; ng-model=&quot;checkbox&quot; /&gt;&#39;)($rootScope); inputElm[0].click(); // Or different trigger mechanisms, such as jQuery.trigger() expect($rootScope.checkbox).toBe(true); }); </code></pre> <p>With this patch, <code>$rootScope.checkbox</code> might not be true, because the click event hasn&#39;t triggered the change event. To make the test, work append <code>inputElm</code> to the app&#39;s <code>$rootElement</code>, and the <code>$rootElement</code> to the <code>$document</code>.</p> <p>After:</p> <pre><code class="lang-js">it(&#39;should update the model&#39;, inject(function($compile, $rootScope, $rootElement, $document) { var inputElm = $compile(&#39;&lt;input type=&quot;checkbox&quot; ng-model=&quot;checkbox&quot; /&gt;&#39;)($rootScope); $rootElement.append(inputElm); $document.append($rootElement); inputElm[0].click(); // Or different trigger mechanisms, such as jQuery.trigger() expect($rootScope.checkbox).toBe(true); }); </code></pre> <h4 id="-input-number-"><strong>input[number]</strong></h4> <p><strong>Due to <a href="https://github.com/angular/angular.js/commit/aa3f951330ec7b10b43ea884d9b5754e296770ec">aa3f95</a></strong>, <code>input[type=number]</code> with <code>ngModel</code> now validates the input for the <code>max</code>/<code>min</code> restriction against the <code>ngM