-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core(full-page-screenshot): use dpr 1 #11688
Conversation
scale: 1, | ||
positionX: 0, |
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.
removing all of this is necessary? IIRC you suggested I add all the parameters in the original PR.
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.
yeah i was being overly cautious back then. i looked and neither CDT nor PPTR uses these props.
i tested this heavily after these changes and feel good that they aren't important.
iffy on |
good question
ya paulirish.github.io/tiny-demos-on-https/pixel-ruler.html?maxPxHeight=20000&color=ccc ya yeaup https://googlechrome.github.io/lighthouse/viewer/?gist=b01f0140619ad5aca1953f532bf85149 |
Thanks for checking.
I don't see any images. |
TRUE! it was fine locally but it put it up on viewer.. and.. looks like some problems. ... investigating... update: oh its just the changes to the FPS audit payload. you changed it in the resolve-nodes branch.. and to verify this PR works.. i merged the two locally.. but the hosted viewer doesn't have the changes. anyway we all good. |
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.
LGTM. Gonna lean on @connorjclark to give the final approval though.
@@ -20,7 +19,7 @@ function createMockDriver({contentSize, screenSize, screenshotData}) { | |||
return contentSize.width; | |||
} | |||
if (code === 'window.devicePixelRatio') { | |||
return screenSize ? screenSize.dpr : 1; | |||
return screenSize ? screenSize.dpr : 2; |
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.
i don't understand this change to the default
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.
good call. it's kind of a separate change. This is the mock driver so we're returning a DPR back to lighthouse.
Since we're now emulating DPR 1 to take the screenshot.. I figured I'd just pretend the browser is a non-1 DPR just to keep things separate
afaik this value is never even used.......
......
okay in that case i'll just delete this part of the mock.
done.
oops I happened to already do a commit like |
followup from #11118 and #11536
I originally hesitated about changing DPR but patrick convinced me here (and in some followup conversations) it's better to change DPR to 1 for our FPS.
Taller image. more coverage. The risk is lower than the risk we already encounter by changing the height (viz observers, etc).
To test this.
node lighthouse-cli https://paulirish.github.io/tiny-demos-on-https/pixel-ruler.html?maxPxHeight=20000 --only-audits=full-page-screenshot --preset=experimental
then in the report: