* The PaginatorConfigurableExample is not added to the examples module and therefore using the latest docs-content inside of `material.angular.io` does not work.
Refactors the entire codebase not to use the patch operators from RxJS, because they pollute the user's setup. Instead, opts into importing the operators directly and chaining them via the `RxChain` class.
Fixes#2622.
Fixes the page being scrolled down if the user presses space to select an option. This is a regression since it used to be handled by the `ListKeyManager`, but it got lost when it was refactored not to disable the default actions.
Adds support for disabling tab links inside of the tab-nav-bar
No longer requires having an extra directive for the ripples of tab links (no exposion of attributes like `mdRippleColor` - which could be flexible but should not be public API here)
Closes#5208
* Currently the `0.0.0-PLACEHOLDER` is still inside of the `package.json` of the material2-builds. Similar as for every other Angular package the version placeholder should be replaced with the version of the current "build commit".
Closes#5320
* Recently the coercing has been moved to the cdk package and now the `material2-builds` repository has a peer dependency on the `cdk-builds`. The readme should be updated to also include the `cdk-builds` installation.
Previously, if a select had no value and the first option was in a group, the group label would go over the trigger, instead of the first option. These changes correct the behavior so the first option is always over the trigger.
Currently, the `menu` role is set on the `md-menu` directive, however the it is inert and won't get rendered inside the overlay. These changes remove the `menu` role from the inert element and set it on the element that will get rendered inside the overlay.
* Fixes an error in the input theming mixin that was caused by a nested mixin.
* Removes the `mat-input-` prefix from the mixin local variables since they're not exposed and don't need to be prefixed.
Fixes#5232.
Currently the autocomplete panel won't close when tapping away on iOS, because the browser doesn't fire the click event on anything that it doesn't consider clickable. These changes add a `touchend` listener that will handle the functionality on mobile.
For buttons and chips the value of the aria-disabled host binding is resolved from a extra method on the class instance.
As already done in other components, the button and chips should just use `boolean.toString()` which is less payload and also makes the code more readable.
Recently the `align` input binding has been removed in favor of the CSS property `text-align`.
If a developer sets the `text-align` property to `end` the text will start from the end and also the input underline will show incorrectly start from the end.
Setting the absolute positioned underline to `left: 0` ensures that the underline always shows-up correctly (because the `mat-input-underline` is inside of a relative container)
Fixes#5272
Fixes an issue that caused IE to reopen the autocomplete panel if the user clicks to select an item. It seems that IE can delay refocusing the input after the panel has been closed, which causes the focus handler to reopen it.
Fixes#5165.
* The tabs demo is the only demo that still overwrites the associated component with CSS that makes it not testable in dark themes (through the dark theme switcher)
* This commit replaces those CSS selectors with CSS that works in dark themes too
* The logfile output should be printed if the tunnel connection can't be established. The logging is also useful to see the update message from Saucelabs for example.
* Removes the `mat-temporary-ink-ripple` mixin from the ripple stylesheet. All components that currently have ripples switched to the ripple component and therefore don't use this mixin.
Resolves a TODO from a while ago to set up the `md-optgroup` to use the typography API. This wasn't done initially since the typography PR and the option group PR got in around the same time.
Moves the `OverlayModule` and the `OVERLAY_PROVIDERS` into the `index.ts`, as opposed to the `overlay-directives.ts`, in order to match the setup in the rest of the modules.
* [Based on the accessibility guidelines](https://www.w3.org/TR/wai-aria-practices-1.1/#dialog_modal), these changes add the `aria-labelledby` to dialog that use `md-dialog-title`, which causes the screen reader to read out the title. E.g. before NVDA would read out "Dialog", but now it reads out "Neptune dialog".
- Looks at the `html` and `body` elements for `dir` attribute and sets the Directionality service value to it
- Whenever someone would try to inject Directionality - if there's a Dir directive up the dom tree it would be provided
fixes#3600
It can happen that the firebase `payloadGithubStatus` function is temporary disabled because a deploy failed (for example due to deploying while function executes).
This leads to a failure inside of the payload CI task because the task is trying to parse the body using JSON (which is not always a JSON response)
It's not worth trying to parse the JSON value since it's only used for debugging and to give an insight what's going on in the functions.
Paul Gschwendtner