fix(material/tooltip): Tooltip should mark for check when visibility … #29000
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
andrewseguin
reviewed
May 4, 2024
andrewseguin
approved these changes
May 4, 2024
…changes This commit fixes an error in the tooltip component where it updates a value used in a host binding without calling `markForCheck`. This does not currently throw an error because `checkNoChanges` is broken for `OnPush` components. However, the error was surfaced when testing an "exhaustive" check that will check _all_ views, regardless of their dirty state. The issue also doesn't really produce a _visible_ problem because it occurs when the tooltip is hidden so the fact that the zoom never updates doesn't make a real difference.
atscott
force-pushed
the
tooltipmarkforcheck
branch
from
758bc86
to
67d97cd
Compare
mmalerba
approved these changes
May 7, 2024
mmalerba
pushed a commit
that referenced
this pull request
May 7, 2024
…changes (#29000) This commit fixes an error in the tooltip component where it updates a value used in a host binding without calling `markForCheck`. This does not currently throw an error because `checkNoChanges` is broken for `OnPush` components. However, the error was surfaced when testing an "exhaustive" check that will check _all_ views, regardless of their dirty state. The issue also doesn't really produce a _visible_ problem because it occurs when the tooltip is hidden so the fact that the zoom never updates doesn't make a real difference. (cherry picked from commit 01540bb)
mmalerba
pushed a commit
that referenced
this pull request
May 7, 2024
…changes (#29000) This commit fixes an error in the tooltip component where it updates a value used in a host binding without calling `markForCheck`. This does not currently throw an error because `checkNoChanges` is broken for `OnPush` components. However, the error was surfaced when testing an "exhaustive" check that will check _all_ views, regardless of their dirty state. The issue also doesn't really produce a _visible_ problem because it occurs when the tooltip is hidden so the fact that the zoom never updates doesn't make a real difference. (cherry picked from commit 01540bb)
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.
…changes
This commit fixes an error in the tooltip component where it updates a value used in a host binding without calling
markForCheck. This does not currently throw an error becausecheckNoChangesis broken forOnPushcomponents. However, the error was surfaced when testing an "exhaustive" check that will check all views, regardless of their dirty state. The issue also doesn't really produce a visible problem because it occurs when the tooltip is hidden so the fact that the zoom never updates doesn't make a real difference.