Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

rely on compositor properties for tab previews #10293

Merged
merged 1 commit into from
Aug 4, 2017
Merged

rely on compositor properties for tab previews #10293

merged 1 commit into from
Aug 4, 2017

Conversation

cezaraugusto
Copy link
Contributor

Auditors: @bsclifton, @luixxiul
close #10291

before checking out this PR

  1. clear session
  2. open two tabs
  3. open devtools (shift+f8)
  4. go to performance tab, record profile
  5. back to tabs, hover over one tab until preview is fired
  6. cancel preview
  7. stop recording profile
  8. go to the profile timeline and select the frames right before and right after preview happens
  9. go to the event log
  10. sort by total time
  11. Keep record (print?) of those numbers

check out this PR and repeat above operation.

numbers should be lower

before
screen shot 2017-08-04 at 12 03 55 am

after
screen shot 2017-08-04 at 12 01 36 am

@cezaraugusto cezaraugusto added this to the 0.18.x Hotfix milestone Aug 4, 2017
@cezaraugusto cezaraugusto self-assigned this Aug 4, 2017
Copy link
Member

@bsclifton bsclifton left a comment

Choose a reason for hiding this comment

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

++

@bsclifton bsclifton merged commit 0b5d58d into master Aug 4, 2017
@bsclifton bsclifton deleted the 10291 branch August 4, 2017 05:58
bsclifton added a commit that referenced this pull request Aug 4, 2017
rely on compositor properties for tab previews
bsclifton added a commit that referenced this pull request Aug 4, 2017
rely on compositor properties for tab previews
bsclifton added a commit that referenced this pull request Aug 4, 2017
rely on compositor properties for tab previews
@@ -83,6 +83,7 @@ html,
height: 100%;
width: 100%;
&.isPreview {
will-change: opacity;
Copy link
Contributor

Choose a reason for hiding this comment

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

nice find! There could be more elements which can be optimized with will-change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes the browser reserves a chunk of memory for that so they're costly if done several times but new tab load and tab's loading animation can benefit too. lmk if you know some other areas. it applies for opacity and transform properties.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tab previews: stick to changing properties that can be handled by the compositor alone
3 participants