animations: When animation is triggered within a disabled zone, the associated event (which an instance of AnimationEvent) will no longer report the totalTime as 0 (it will emit the actual time of the animation). To detect if an animation event is reporting a disabled animation then the event.disabled property can be used instead.

We think this order will be less confusing when the control is checked directly. You will only need to update your app if it has relied on this bug to keep track of the old control value. If that is the case, you should be able to track the old value directly by saving it on your component.

platform-server: * Bump the dependency on Domino to 2.0 to resolve issues with namespacing

forms: – AbstractControl#statusChanges now emits an event of ‘PENDING’ when you call AbstractControl#markAsPending

Previously it did not emit an event when you called markAsPending

To migrate you would need to ensure that if you are filtering or checking events from statusChanges that you account for the new event when calling markAsPending

animations: When animation is trigged within a disabled zone, the associated event (which an instance of AnimationEvent) will no longer report the totalTime as 0 (it will emit the actual time of the animation). To detect if an animation event is reporting a disabled animation then the event.disabled property can be used instead.

The 2.6 version of Typescript’s “resolveModuleName” started to require paths passed to be separated by ‘/’ instead of being able to handle ».

Move init hooks into TView

Correct onDestroy order for projected components

Add type and hooks to directive def

Enable size tracking of a minimal CLI render3 application

Fix platform-detection example for Universal

Add canonical view query

Some enhancements on compiler to reflect changes

Rename QueryPredicate to LQuery

Rename LQuery to LQueries and associated renames

Allow HttpInterceptors to inject HttpClient :

Previously, an interceptor attempting to inject HttpClient directly would receive a circular dependency error, as HttpClient was constructed via a factory which injected the interceptor instances. Users want to inject HttpClient into interceptors to make supporting

Either HttpClient or the user has to deal specially with the circular Dependency. This change moves that responsibility into HttpClient itself. By utilizing a new class HttpInterceptingHandler which lazily Loads the set of interceptors at request time, it’s possible to inject HttpClient directly into interceptors as construction of HttpClient no longer requires the interceptor chain to be constructed.

Add navigationSource and restoredState to NavigationStart :

Currently, NavigationStart there is no way to know if navigation was triggered imperatively or via the location change. These two use cases should be handled differently for a variety of use cases (e.g., scroll position restoration). This PR adds a navigation source field and restored navigation id (passed to navigations triggered by a URL change).

Removes generation of comments

Fix SideNav height on narrow screens :

Since we specify `bottom: 0`, specifying the height is unnecessary and Leads to wrong height (unless updated) on narrow screens where the topbar height is decreased.