Skip to content

fix(progress-spinner): non-default diameter indeterminate animation not working inside Shadow DOM #16177

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 1 commit into from
Jun 4, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jun 1, 2019

Fixes animating a progress spinner with a non-default diameter in indeterminate mode not working if the element is inside of a shadow root. The issue is that we always add the style tag with the animation to the document.head which doesn't pierce through the Shadow DOM.

Also adds a some more test coverage for the style tag insertion logic.

Fixes #16172.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround G This is is related to a Google internal issue target: patch This PR is targeted for the next patch release labels Jun 1, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 1, 2019
@crisbeto crisbeto force-pushed the 16172/spinner-shadow-dom branch 2 times, most recently from fab4566 to 9e8a2f7 Compare June 1, 2019 10:20
@josephperrott
Copy link
Member

@crisbeto Can you rebase when you have a chance?

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

…ot working inside Shadow DOM

Fixes animating a progress spinner with a non-default diameter in indeterminate mode not working if the element is inside of a shadow root. The issue is that we always add the `style` tag with the animation to the `document.head` which doesn't pierce through the Shadow DOM.

Fixes angular#16172.
@crisbeto crisbeto force-pushed the 16172/spinner-shadow-dom branch from 9e8a2f7 to d05d9ca Compare June 3, 2019 18:52
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jun 3, 2019
@crisbeto
Copy link
Member Author

crisbeto commented Jun 3, 2019

Rebased.

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

@josephperrott josephperrott merged commit c116533 into angular:master Jun 4, 2019
josephperrott pushed a commit that referenced this pull request Jun 10, 2019
RudolfFrederiksen pushed a commit to RudolfFrederiksen/material2 that referenced this pull request Jun 21, 2019
@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 G This is is related to a Google internal issue P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MatSpinner indeterminate doesn't work inside of a shadow root
4 participants