Skip to content
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

fix(drag-drop): incorrectly preserving transform if root element changes #14697

Merged
merged 1 commit into from
Jan 16, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jan 2, 2019

Currently we cache the element's initial transform so that we can preserve it after the user has dragged it, however if the root element changes, the cached value will be incorrect. These changes reset the cached value if the root element changes.

Currently we cache the element's initial transform so that we can preserve it after the user has dragged it, however if the root element changes, the cached value will be incorrect. These changes reset the transforms if the root element changes.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jan 2, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 2, 2019
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 added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 10, 2019
@vivian-hu-zz vivian-hu-zz merged commit 3656a4e into angular:master Jan 16, 2019
@JurajMlich
Copy link

@crisbeto does this fix #14703 ?

@crisbeto
Copy link
Member Author

No, it doesn't.

s2-abdo pushed a commit to s2-abdo/material2 that referenced this pull request Jan 18, 2019
…ges (angular#14697)

Currently we cache the element's initial transform so that we can preserve it after the user has dragged it, however if the root element changes, the cached value will be incorrect. These changes reset the transforms if the root element changes.
s2-abdo pushed a commit to s2-abdo/material2 that referenced this pull request Jan 18, 2019
…ges (angular#14697)

Currently we cache the element's initial transform so that we can preserve it after the user has dragged it, however if the root element changes, the cached value will be incorrect. These changes reset the transforms if the root element changes.
vivian-hu-zz pushed a commit that referenced this pull request Jan 18, 2019
…ges (#14697)

Currently we cache the element's initial transform so that we can preserve it after the user has dragged it, however if the root element changes, the cached value will be incorrect. These changes reset the transforms if the root element changes.
@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 10, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants