Currently the default stroke of a spinner is always 10px which doesn't look great on anything that's smaller than the default. These changes switch it to be 10% of the circle's diameter.
* Re-adds the `openedStart` and `closedStart` events due to popular demand.
* Fixes wrong signature for the returned promise from toggle. The signature states that the resolved value is supposed to be a `MatDrawerToggleResult` while in practice it was `undefined`.
* No longer marks the `Platform` service from `@angular/cdk/platform` as `docs-private`. The platform service should be documented since it's useful and likely the only thing in the platform entry-point.
* Generates a `material-ripple.html` API file in the material docs content. This can be used to show the ripple API information in material.angular.io.
* fix(MatPaginatorIntl): Provide a provider if exists.
If there is already a MatPaginatorIntl provider that one
If not create a new instance.
Closes#7344
* style(paginator): Changed arguments, removed spacing
* style(paginator): Changed argument name.
After some refactoring, the `ScrollDispatcher` no longer dispatches inside the `NgZone`, which caused the `CloseScrollStrategy` to break, because it detaches without triggering change detection. These changes bring the detachment back into the `NgZone`.
Fixes#7922.
Currently the `detachments` stream will emit any time the `detach` or `dispose` methods are called, which doesn't reflect actual detachments. It is something I noticed while looking into #7922.
* Currently the `ViewportRuler` caches the `ClientRect` of the `document.documentElement` which is only used for determining the scroll position and is being updated on demand anyway. These changes switch to caching the `innerWidth` and `innerHeight` which was the original intent.
* Adds a `getViewportSize` method that returns the cached viewport width and height. The reasoning is that for all of the cases where we were using `getViewportRect`, we were only taking the `width` and `height`. `getViewportSize` helps us avoid the overhead from determining the `top`, `bottom`, `left` and `right` via the scroll position.
The `FocusMonitor` works by binding a `touchstart` (as well as some other events) listener to the `document` in order to keep track of focus. These changes make the `touchstart` listener `passive`, which means that on supported browsers it won't block rendering and should make scrolling smoother.
Currently chips that are selected programmatically (e.g. by setting the of `ngModel`) will moves focus to themselves, causing the page the scroll down. This can be observed in the demo app where the bottom chip instances have a preselected value which shifts focus to the bottom. These changes fix the issue by only moving focus if the selection was a result of a user interaction.
Removes the `DIRECTIONALITY_PROVIDER` since it isn't being used anywhere. This seems to be a remnant of the old approach to dealing with directionality.
The behavior where we don't allow new dialogs to be opened while a dialog is animating was introduced initially in #5769 to avoid issues where the user might open multiple dialogs by accident if they press enter one too many times. This is problematic because it also means that the consumer is blocked from opening dialogs for certain 300ms intervals. These changes approach the issue differently by moving focus onto the dialog container immediately while it's animating.
Fixes#6560.
Joey Perrott