-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix headed Chrome screenshot #93
Conversation
7df44f8
to
06f8c3f
Compare
@@ -30,6 +30,7 @@ export async function focusElem(elem) { | |||
|
|||
export async function hoverAt(x, y) { | |||
await sendMouse({ type: 'move', position: [x, y] }); | |||
if (window.d2lTest) window.d2lTest.hovering = true; |
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.
Would having the vdiff/pause stuff just add a listener on the window or body for mouseover
also work? If so, it might be nice for that code to live over there where it belongs.
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.
Talked offline. Sticking with this for now to avoid overusing inlineStyles
, which is yucky and slow.
06f8c3f
to
2e72225
Compare
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.
Crazy that we need to do this, but also crazy that it works!
Yeah, I'd definitely like to get rid of it sooner rather than later if possible. |
🎉 This PR is included in version 0.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes headed Chrome screenshots by inlining all styles to capture hover effects before they break.