Skip to content

docs: hammerjs using systemjs.config #10711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 37 commits into from
May 9, 2018
Merged

docs: hammerjs using systemjs.config #10711

merged 37 commits into from
May 9, 2018

Conversation

Longfld
Copy link
Contributor

@Longfld Longfld commented Apr 5, 2018

Replace #10653

@Longfld Longfld requested review from amcdnl and jelbourn as code owners April 5, 2018 01:14
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 5, 2018
@Longfld Longfld changed the title Bring fork up to date docs: hammerjs using systemjs.config Apr 6, 2018
crisbeto and others added 19 commits April 6, 2018 16:40
Fixes an error that is being thrown when opening a tooltip, closing it and updating its position.
)

Similarly to other controls that are based around an input and a popup, the datepicker should open on alt + down arrow and close on alt + up arrow. The opening logic was already being handled and this PR adds the logic for closing.
…r#10661)

Fixes the underlying `MatTabBodyPortal` not cleaning up correctly on destroy, because it overrides the `ngOnDestroy` method from the `CdkPortalOutlet`. Also does some general cleanup around the tab body component.
Moves a timeout, that only has some DOM-related logic, to run outside the `NgZone`.
Moves some duplicated logic for coercing CSS values under `cdk/coercion` and replaces the usages.
…osition with a viewport margin (angular#10650)

Fixes the `bottom` value and the viewport margin not being calculated correctly when using the `FlexibleConnectedPositionStrategy` with a flexible height and a viewport margin.
…ngular#10644)

Fixes the horizontal stepper cutting off the bottom part of its content due to it having `overflow: hidden`. These changes scope the `overflow` only to when the stepper is collapsed.

Fixes angular#10634.
* Fixes all of the RTL selectors being scoped to the badge itself, rather than a parent, which means that consumers would have to set `dir="rtl"` on each individual badge.
* Fixes none of the `left`/`right` values being inverted.
…gular#10629)

Fixes the width of the autocomplete panel not being recalculated when the viewport size changes.
Fixes a few instances in the `table`, `sort` and `paginator` modules where the spacings weren't being inverted in RTL layouts.
Currently most of the timeouts inside the `FocusMonitor` are run outside the `NgZone`, because they're called from event listeners that are bound on the outside, however the one from `_setOriginForCurrentEventQueue` can still end up inside when it's called by `focusVia`.
…gular#10605)

Fixes the button toggle setting the `aria-label` of its underlying input to a blank value by default.
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla and removed cla: yes PR author has agreed to Google's Contributor License Agreement labels Apr 6, 2018
@Longfld
Copy link
Contributor Author

Longfld commented Apr 6, 2018

I confirm that I am ok with my commits being contributed to this project.

@josephperrott josephperrott added cla: yes PR author has agreed to Google's Contributor License Agreement and removed cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla labels May 3, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@josephperrott
Copy link
Member

Verified signed CLA.

@josephperrott
Copy link
Member

@Longfld it looks like you still have some failing tests on CI, can you rebase and push again.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla and removed cla: yes PR author has agreed to Google's Contributor License Agreement labels May 3, 2018
@Longfld
Copy link
Contributor Author

Longfld commented May 3, 2018

@josephperrott
I've got this error, any suggestion where I was wrong? any particular tag I should merge?

"ci/angular: merge status — Missing required labels: "target: *", "cla: yes", forbidden lab"

@josephperrott josephperrott added cla: yes PR author has agreed to Google's Contributor License Agreement target: master only and removed cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla labels May 7, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@josephperrott
Copy link
Member

You should not need to worry about the ci/angular status as it is mostly made up of checks that are based on the Material team applying labels and such.

Verified signed CLA.

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels May 7, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn merged commit d4cfea1 into angular:master May 9, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.