fix(platform-browser): wait until animation completion before destroying renderer#50677
fix(platform-browser): wait until animation completion before destroying renderer#50677alan-agius4 wants to merge 0 commit intoangular:mainfrom
Conversation
233f2f5 to
979c7a1
Compare
|
TGP. Caretaker note: TGP is failing but it seems that this changes improves the screenshots as previously there was some unstyled content. |
jessicajaniuk
left a comment
There was a problem hiding this comment.
LGTM! This looks much cleaner than what was there before.
|
Caretaker note: this change required a bulk screenshots update in G3 as this causes some diffs. This fixes a real bug as some content in the reference images is unstyled but is now correctly styled. A CLI that requires global approval is needed, please see discussion in https://angular-team.slack.com/archives/G011LHKQM1Q/p1686585245856779. |
|
FYI, adding the "blocked" label for now, since landing this PR needs coordination. We plan to land it on Monday (06/26). |
|
This PR was merged into the repository by commit d227347. |
This commit removes unnecessary castings. PR Close #50677
…ing renderer (#50677) Prior to this commit, the renderer destroy method was being called before the animation complete. This is problematic when using `REMOVE_STYLES_ON_COMPONENT_DESTROY` as it causes the styles to be removed too early. This commit, updates this destroy logic to be call the render destroy once the animations complete. This has been reported internally in: - http://b/271251353#comment12 - http://b/282004950#comment5 PR Close #50677
This commit removes unnecessary castings. PR Close #50677
This reverts commit d227347.
… destroying renderer (angular#50677)" This reverts commit 2b55103.
979c7a1 to
39935ee
Compare
…ing renderer (angular#50677) Prior to this commit, the renderer destroy method was being called before the animation complete. This is problematic when using `REMOVE_STYLES_ON_COMPONENT_DESTROY` as it causes the styles to be removed too early. This commit, updates this destroy logic to be call the render destroy once the animations complete. This has been reported internally in: - http://b/271251353#comment12 - http://b/282004950#comment5 PR Close angular#50677
This commit removes unnecessary castings. PR Close angular#50677
…" (angular#50857) This reverts commit d227347. PR Close angular#50857
… destroying renderer (angular#50677)" (angular#50857) This reverts commit 2b55103. PR Close angular#50857
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…ing renderer (angular#50677) Prior to this commit, the renderer destroy method was being called before the animation complete. This is problematic when using `REMOVE_STYLES_ON_COMPONENT_DESTROY` as it causes the styles to be removed too early. This commit, updates this destroy logic to be call the render destroy once the animations complete. This has been reported internally in: - http://b/271251353#comment12 - http://b/282004950#comment5 PR Close angular#50677
This commit removes unnecessary castings. PR Close angular#50677
Prior to this commit, the renderer destroy method was being called before the animation complete. This is problematic when using
REMOVE_STYLES_ON_COMPONENT_DESTROYas it causes the styles to be removed too early.This commit, updates this destroy logic to be call the render destroy once the animations complete.
This has been reported internally in: