* Hides the warnings about unresolved TypeScript symbols for the mixin base classes. Those warnings are not fixable and are polluting the Dgeni output.
* Adds missing `@deprecated` tags to entries that already have the `@deletion-target` set.
* Updates to the latest version of dgeni-packages because https://github.com/angular/dgeni-packages/commit/3a4e5685589b99b85dfb88e8fd8dbf46aab24088 landed.
Since we have some cases where we pass in positions verbatim to the connected position strategy (the connected position directive), we could end up in a situation where the consumer passed in a set of invalid positions that don't break necessarily, but don't work correctly either. These changes add some sanity checks at runtime to make debugging easier.
* Reworks the tooltip to reuse the `OverlayRef` after the first time it is opened, rather than destroying it and creating a new one for every subsequent open. This reduces the overhead from having the create the new overlays all the time.
* Changes the signature of the `ConnectedPositionStrategy.withScrollableContainers` method to return the position strategy. This is primarily for consistency with the other methods.
In some situations, the `disable()` method of a form control is called while the datepicker input is focused. This causes a changed after checked error.
Normally, native input elements automatically blur if they turn disabled. This behavior is problematic, because it would mean that it triggers another change detection cycle, which then causes a changed after checked error if the input element was focused before.
Fixes#9559
Adds a simple "aria-describedby" input in the manner of "aria-labelledby."
The ability to set "aria-describedby" is essential for accessible radio buttons,
as the attribute allows further description of a radio button to be read
after mentioning the button's label and whether or not it is checked.
Since there's a timeout when announcing something through the `LiveAnnouncer.announce` method, it may be hard/prone to race conditions for the consumer to coordinate it with some other action. These changes expose a promise that will be resolved once the message has been added to the DOM.
Brings the autocomplete escape key behavior on IE in line with other browsers. Currently pressing escape on IE will cause it to revert the display value to the one it had on focus, however it won't dispatch any events and the model value will be out of sync. None of the other browsers (event Edge) have this behavior.
* Switches to using the `width` and `height` from the `OverlayConfig`, rather than the properties on the `GlobalPositionStrategy`.
* Deprecates the `GlobalPositionStrategy.width` and `GlobalPositionStrategy.height` methods in favor of passing the dimensions through the config.
* Reworks the `GlobalPositionStrategy` testing setup to make it less prone to breaking if any of the `OverlayRef` internals change.
Fixes#9715.
Right now, the ripple container for the checkbox, radio and slide-toggle are positioned using SCSS calculations. This works fine, but limits people, who want to resize the inner container (e.g. smaller checkbox).
Since resizing the checkbox to be smaller is reasonable, because MDC and the specs seem to have smaller boxes (18x18), the ripple container position can be determined using a simple CSS `calc`.
References #9244. References #9210.
* Updates the slide-toggle, radio and checkbox ripples to have a quicker enter animation. This aligns more with the behavior MDC provides, and also feels more appropriate (for focus indicators) and is also more aligned with the specs.
Currently the stepper tests are structured into completely different suites for vertical and horizontal steppers where the common tests are pulled out into functions which are called in each suite. This makes it harder to navigate and debug, in addition to flooding the logs with unnecessary data if one of the tests fails. These changes combine the tests into one suite with a couple of sub-suites that cover only the functionality that is exclusive to particular stepper variant.
* Improves the accessibility for `mat-flat-button` elements in high-contrast mode. Currently it's nearly impossible to figure out, whether it's a button or not.
* add max/min filter to multi year and year views
* address @mmalerba's comments
* fix and tighten up logic
* possibility to have a null filter in month view
* feat(datepicker): @Output of year and month selected in multiyear/year
views
* address @mmalerba's comments
* address comments
* add types to some outputs
* fix wrong parameter type
* restore accidentally removed object
* example and docs text
* change emitted values to objects instead of just numbers
* change datepicker.md and switch back tslint configs
* fix nit
* Remove changes in demo app
* Adds an initial implementation of the new `MatBottomSheet` service that allows users to display component-based or template-based bottom sheets.
* Sets up the various boilerplate and infrastructure necessary for a new component.
Note: this is an initial implementation that has the necessary functionality, styles and accessibility. More docs, examples and touch gestures will be added in a follow-up.
* feat(form-field): support for different spec variants (#9366)
* feat(form-field): implement hover state
[Based on the spec](https://material.io/guidelines/components/text-fields.html#text-fields-states) form fields should have a hover state where the underline gets darkened while the user is hovering and gets replaced by the theme color after the focus the input.
* branch css logic
* extract underline css into standard variant
* box variant underline
* box variant spacing
* add legacy variant
* fix select ellipsis
* move hover state changes out of legacy variant
* add variants section to input demo
* use filter/backface-visibility to address label jumpiness
* address comments
* fix box variant text fuzziness
* remove bluriness fixes that aren't needed anymore
* address comments
* remove the floatLabel=never option in the new variants
* variant --> appearance
* add tests for new label & placeholder behavior
* update demo to use mat-label
* fix bazel build
* feat(chips): Add chip avatar and chip trailing icon (#9557)
* feat(chips): Add chip avatar and chip trailing icon
* Removed MatBasicChip and MatStandardChip
* Add mat-chip-trailing-icon style to MatChipRemove and add examples in
demo
* fix(form-field): rename box to fill and tweak the styles a bit (#9636)
* make some tweaks to the box appearance
* rename 'box' appearance to 'fill'
* feat(form-field): add outline style (#9705)
* remove datepicker reliance on form-field's underlineRef
* add spacing and alignment rules for outline variant
* outline color & thickness
* style tweaks
* correctly position and size the gap
* address comments
* fix(form-field): correct prefix & suffix icons as well as select arrow for various form field appearances (#9743)
* feat(input): add utilities for custom styling and monitoring state of input autofill (#9719)
* add utility for monitoring input autofill
* add scss mixin for styling input autofill colors
* tests
* move everything from cdk to MatInputModule
* address comments
* add doc comments
* fix(form-field): fixes for outline appearance (#9759)
* use the `AutofillMonitor` in `MatInput`
* Make `updateOutlineGap` public so users can call it if needed
* feat(chips): add ripple to chips (#9761)
* fix(form-field, chips): fix tests & lint (#9767)
* undo change that caused darkened color for legacy form field
* fix change detection
* fix(chips): remove margin for chip list (#9793)
* add terminateOnPointerUp to ripple config
* No longer allows publishing versions that include "beta" / "alpha" / "rc" to the "latest" tag on NPM. This safeguard can be still removed temporarily, if there is a real need to publish a beta in the latest tag.
Closes#9699.
Fixes the value being typed inside an `input[type="number"]` getting assigned to the model as a string. Normally this is handled by the `NumberValueAccessor` from the forms module, however the autocomplete is its own value accessor and as such has to handle it on its own.
Fixes#9628.
* Clears out all of the registered listeners in the `UniqueSelectionDispatcher` when the module is unloaded to avoid potential memory leaks due to references inside the listeners.
* Cleans up the unit test setup for the dispatcher to align it with the rest of the project.
* feat(ripple): support ripple fade-out on pointer up
By default, ripples in Angular Material will only fade out if the pointer is released and the enter animation completed. This behavior is similar in the MDC implementation of the Material Design guidelines.
In some scenarios, developers prefer fading out the ripples immediately on pointer release. Similarly the Material Design guidelines also have some videos that show ripples that seem to follow that behavior as well. To be able to provide the necessary flexibility (as we already did with the animation durations), the `terminateOnPointerUp` global option has been added.
Closes#9577
* Comment improvements
* Remove unnecessary whitespace
Adds an `exportAs` to the `MatAutocompleteTrigger` so it can be accessed through templates and because the methods for toggling the panel are on it.
Fixes#9687.
Paul Gschwendtner