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.
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
devtools: enable sticky header, top bar, and report ui features #9023
devtools: enable sticky header, top bar, and report ui features #9023
Changes from 36 commits
41aa187
000f841
c0bf21d
1e040cc
a6e722e
7129ae1
ca0afd1
4a6a796
fe61b86
720dbb4
0153c0e
009c7d2
0ee54c8
cc763f8
7ace084
6650b66
8063f18
63c9638
739b20a
4b86fb4
bdbf379
181a5ed
2031b5e
b2016ea
f16f78f
e3a4ba0
19215e9
6059968
9dd16c1
82bb8e6
aec1ac3
0c1b09e
656e941
8ded84e
6dabf64
df79fcb
427baf5
d383120
b6879b1
26f2864
018a64b
2f3da14
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using the ResizeObserver in the deploy report (It's disabled outside devtools but if you revert that bit), and add some logging to the callback:
You see that the position of our
topbar
is jumping all over the place!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we should just disable it outside DevTools for now, luckily it works there perfectly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since in theory
ResizeObserver
is more efficient and the future path to monitoring resizes, what about// Use ResizeObserver where available. TODO: there is an issue with incorrect position numbers and, as a result, performance issues due to layout thrashing. See https://github.com/GoogleChrome/lighthouse/pull/9023/files#r288822287 for details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you also suggesting removing the devtools check?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whoops, no, good point. I like your version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
evidence number 25 that these different uses of the score gauges should share less than they do :)