Skip to content

fix(material/tooltip): resolve server-side rendering error #25728

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
Oct 3, 2022

Conversation

crisbeto
Copy link
Member

In a recent change MDC introduced a top-level reference to window which broke our server-side rendering check. These changes remove our dependency on MDC completely in order to fix the error.

In a recent change MDC introduced a top-level reference to `window` which broke our server-side rendering check. These changes remove our dependency on MDC completely in order to fix the error.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: major This PR is targeted for the next major release labels Sep 30, 2022
Copy link
Contributor

@wagnermaciel wagnermaciel left a comment

Choose a reason for hiding this comment

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

LGTM. I'm assuming the top level reference to window not relevant to any of the constants we use?

@crisbeto
Copy link
Member Author

crisbeto commented Oct 3, 2022

No, the error was happening because the values were being passed through the trusted types API.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 3, 2022
@crisbeto crisbeto merged commit 9769a5a into angular:main Oct 3, 2022
@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 Nov 3, 2022
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 P2 The issue is important to a large percentage of users, with a workaround target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants