Skip to content
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

Automate jumpiness test cases #6986

Open
pcwalton opened this issue Aug 5, 2015 · 4 comments
Open

Automate jumpiness test cases #6986

pcwalton opened this issue Aug 5, 2015 · 4 comments
Labels

Comments

@pcwalton
Copy link
Contributor

@pcwalton pcwalton commented Aug 5, 2015

It's tricky to automate them, but we should try.

For posterity, jumpiness here refers to incorrect dynamic restyling that causes fragments to jump around as you hover over them with the mouse.

@jdm jdm added the A-testing label Aug 5, 2015
@jdm
Copy link
Member

@jdm jdm commented Aug 5, 2015

What is it about mouse hovering that triggers the problem?

@pcwalton
Copy link
Contributor Author

@pcwalton pcwalton commented Aug 5, 2015

It's the most common way to effect a restyle.

I imagine that having restyle hints that allow us to avoid restyling on hover will cover up these issues too, but that'd just be a cover-up: fundamentally, these are dynamic restyling/reflow bugs.

@glennw
Copy link
Member

@glennw glennw commented Aug 5, 2015

It would be fairly trivial to modify the is_ready_to_paint_image_output() infrastructure to trigger and wait for a specified number of (non)incremental reflows before writing the image. Would something like this do the job?

@pcwalton
Copy link
Contributor Author

@pcwalton pcwalton commented Aug 5, 2015

My problem actually was that I couldn't actually trigger the problem from script at all. For some reason only hover caused the issue.

My current hypothesis is that it has something to do with the node damage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.