sync from upstream #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* When programmatically calling `launch` on the ripple element the developer can specifiy a configuration object. Since the `launch` method is part of the directive and all the associated `@Input`s. The given configuration should be used as default. * Exposes the ripple component instance to the Angular template.
…lts to gcs & firebase (#2774) * Add google cloud storage * Add screenshots to e2e test * Renamed functions. Add types. Remove firebase, use firebase-admin * dependencies * Save pull request sha to firebase db * Save travis job id * Add function to update github commit status * remove update status code * Add update status * Address comments * Add fs-extra * try using ES6 Promise * . * Fix cannot find name promise * Add back function to save filenames to firebase * Update comments
Adds a `dismiss` method to the snack bar service, which dismisses the currently-open instance, mostly for convenience since the spec only allows one snack bar to open at a time.
Change the docs to align with the returned observable
Currently the tooltip always binds the mouseenter and mouseleave events, however this can cause the click handlers on the tooltip host not to be fired on the first tap. These changes switch to binding the events only on devices that have touch events. Fixes #2326.
* Add a focus overlay for button-toggle * Use FocusOriginMonitor * . * Fix test * Add 0.12 opacity white and black. * Add dark-overlay
* add throw operator * log error message instead of object
* fix(pseudo-checkbox): alignment issue and border color * Fixes an alignment issue with the pseudo checkboxes. Most likely caused by the `mat-` prefix changes or a faulty conflict resolution. * Fixes pseudo checkboxes not using the proper border color from the theme. * Adds the pseudo checkboxes to the checkbox demo for easier testing. * fix: address PR feedback
* Fixes the ripple not being clipped in compatibility mode. The issue was due to the check not including the `mat-` selectors. * Reduces the amount of DOM manipulation done by the button. Fixes #3164.
* Adds enter/exit animations to the dialog. * Refactors the `MdDialogContainer` and `MdDialogRef` to accommodate the animations. * Fixes some test failures due to the animations. * Allows for the backdrop to be detached before the rest of the overlay, in order to allow for it to be transitioned in parallel. Fixes #2665.
* . * Try to make screenshot image size same as before * change back to 1024 x 768
* update: add button to toggle theme in demo-app * Adds a button to the demo-app toolbar that allows developers to quickly change between dark and light Material themes. This is very useful when building new components or just when confirming that all components work with dark themes. * Improve list-demo in dark-theme * Fix stylelint * Address comments
* Now triggers the ripple on label mousedown (similar as to slide-toggle and radio) * Only sets cursor for underlying `label` element (similar as for native checkbox inputs) * Adds a test that confirms that ripples work for checkbox Fixes #3030
* Adds an option to disable ripples for slide-toggle elements. Similar as for buttons, checkbox and other components.
…3232) * Use a lighter color for focused layer in button-toggle * . * Only show focus layer when keyboard focus
Prevents the autocomplete being opened on load in IE. This was due to a bug where IE fires the `input` event on `load`, `focus` and `blur`, if the input element has a placeholder. Fixes #3183.
* fix(tooltip): wrong position when using OnPush change detection Fixes the tooltip having a wrong position if it is inside a component with `OnPush` change detection. The issue was due to the fact that when `OnPush` is used, the tooltip text isn't rendered at the moment when the element is positioned. Fixes #3497.
* Wraps multi-line text, instead of truncating it, inside of snack bars. **Note:** While the spec only mentions multi-line text on mobile, this seems to be a better approach than cutting it off at ~500px. We can revisit this if we start using media queries. * Aligns the snack bar button margin to the spec. * Simplifies some of the CSS to remove the need for a hardcoded height and negative margins. Fixes #1951.
#2989) This fixes positioning issues when rendering templates which contain embedded templates. The templates need to be rendered in order to properly determine width which can then determine placement.
* fix(button): ripple color for raised buttons * Fixes the incorrect ripple color for raised buttons. Currently the ripple color is always based on black. This is incorrect on palettes like Indigo. Fixes #2901 * Address feedback * Distinguish between buttons with focus overlay * Fix comment
* The checkbox and radio disable the ripples using a `*ngFor` check. This causes the `ViewChildren` instance to turn null. The reference is required for the focus indicators. * If ripples are disabled there will be still ripples on click. This is due to the fact that label elements redirect focus to the underlying input element. The `focusOrigin` is therefore `program` and a focus ripple will show up. * Tests had to be adjusted because the `[md-ripple]` element won't be removed anymore. Therefore the tests now confirm that no ripples are showing up. Fixes #3856.
Fixes the size of icons inside dense lists. Fixes #3886.
* Switches the `translate` to `translate3d` for hardware accelerated animations.
Fixes a reference error being thrown by the theme check when using server-side rendering. Fixes #3870.
Throws a slightly better error when the wrong prefix is used. The error now includes the node name of the offending element, which should make it easier to pinpoint the issue.
* Fixes the karma pattern warnings. Those showed up because there was a pattern that included all files (and watched them).
* Introduces a version placeholder (as in angular/angular) that will be replaced with the version string form the root `package.json` file. * This ensures that the different packages are always having the correct version and it also ensures that there is no version-mismatch.
* Due to a typo the `README.md` file is not copied properly to the releases.
* Removes two unused bash scripts (`copy-docs.sh`, `enact-release.sh`). * `enact-release.sh` is now part of the release gulp task. * `copy-docs.sh` is now part of the `docs` gulp task.
* build: dgeni add deprecated marker * Adds a class to property rows in the template that can be used to distinguish between deprecated and stable APIs. Fixes #3981. * Address feedback
* Creates sourceMap files for all bundles inside of the release. Fixes #852
* build: detect todos in public comments * Creates a naive rule that checks all multi-line comments and reports failures once it detects TODOs inside of it. * This means that TODOs always need to placed inside of single-line comments. Fixes #4026
* Removes the unused `public` folder from the repository.
Currently when using the `mdTextareaAutosize` directive the textarea height might be incorrect on component initialization. This happens because the textarea `scrollHeight` property is not ready in the `ngOnInit` lifecycle hook yet. Other libraries like `angular-elastic` have timeouts for that. But using the `ngAfterViewInit` lifecycle hook is more elegant and also ensures that the `scrollHeight` property is ready. Also switches `offsetHeight` to `clientHeight` since we don't want to include the border in our line-height calculations. Also by default `textarea` elements have a padding of `2px` and the `padding` needs to be explicitly set to `0px` when resolving the line-height. Fixes #4070.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.