Uh oh!
There was an error while loading. Please reload this page.
perf(overlay): remove detached overlays from the DOM - #12414
Merged
jelbourn merged 1 commit intoAug 1, 2018
Conversation
jelbourn
commented
Jul 27, 2018
Contributor
Will this conflict with #11806? |
crisbeto
commented
Jul 27, 2018
MemberAuthor
As far as I can tell no, because the overlay in #11806 never detaches, it just toggles |
jelbourn
approved these changes
Jul 28, 2018
| private _backdropClick: Subject<MouseEvent> = new Subject(); | ||
| private _attachments = new Subject<void>(); | ||
| private _detachments = new Subject<void>(); | ||
| private _previousHostParent: HTMLElement; |
Contributor
There was a problem hiding this comment.
Add a description for this that explains how its used?
Removes the detached overlays from the DOM, rather than keeping their host element. Previously we kept the elements in the DOM, because they don't interfere with user interactions and it made it easier to handle animations, however doing so can cause scroll jank, because the host still has dimensions and is being rendered by the browser. Fixesangular#12341.
crisbetoforce-pushed
the
12341/overlay-remove-bounding-box
branch
from
July 28, 2018 07:31
1319612 to
ed490c4Comparejelbourn pushed a commit
that referenced
this pull request
Aug 7, 2018
Removes the detached overlays from the DOM, rather than keeping their host element. Previously we kept the elements in the DOM, because they don't interfere with user interactions and it made it easier to handle animations, however doing so can cause scroll jank, because the host still has dimensions and is being rendered by the browser. Fixes#12341.
jelbourn pushed a commit
that referenced
this pull request
Aug 7, 2018
Removes the detached overlays from the DOM, rather than keeping their host element. Previously we kept the elements in the DOM, because they don't interfere with user interactions and it made it easier to handle animations, however doing so can cause scroll jank, because the host still has dimensions and is being rendered by the browser. Fixes#12341.
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. |
This file contains hidden or 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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

Removes the detached overlays from the DOM, rather than keeping their host element. Previously we kept the elements in the DOM, because they don't interfere with user interactions and it made it easier to handle animations, however doing so can cause scroll jank, because the host still has dimensions and is being rendered by the browser.
Fixes#12341.