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

Inset box shadow rendering bug #2068

Closed
nc4rrillo opened this issue Nov 21, 2017 · 7 comments
Closed

Inset box shadow rendering bug #2068

nc4rrillo opened this issue Nov 21, 2017 · 7 comments

Comments

@nc4rrillo
Copy link
Contributor

@nc4rrillo nc4rrillo commented Nov 21, 2017

While browsing this docs.microsoft.com page I noticed strange lines in the tree view on the left.

If you look at this page you'll notice extra lines being drawn for inset box shadows compared to FF Nightly with WR off.

Setting any of the values to non-zero causes the issue to go away.

@nc4rrillo
Copy link
Contributor Author

@nc4rrillo nc4rrillo commented Nov 21, 2017

Tested this on Linux with an Intel GPU and on Windows 10 with an nVidia GPU. Seems to be affected by the page zoom in FF.

@nc4rrillo
Copy link
Contributor Author

@nc4rrillo nc4rrillo commented Nov 21, 2017

I've tried to recreate this in a sample app but I can't trigger the weird behavior, wondering if its Gecko specific or if I have the conditions that trigger it wrong.

@nc4rrillo
Copy link
Contributor Author

@nc4rrillo nc4rrillo commented Nov 21, 2017

@Darkspirit
Copy link

@Darkspirit Darkspirit commented Nov 21, 2017

This is a regression from Nightly's perspective: https://bugzilla.mozilla.org/show_bug.cgi?id=1419528#c2
(a624aa6...7892f53)

(Radeon RX480 @ Debian Testing, KDE)

@glennw
Copy link
Member

@glennw glennw commented Nov 21, 2017

These glitches often depend on the contents of the surface cache and the allocation patterns, so it might be quite difficult to hand-craft a test case. What I normally do in these cases is do a binary wrench recording (export ENABLE_WR_RECORDING=1) from Gecko - and then replay this file in wrench. If we can reproduce it that way, it's normally quite easy to reduce the test case and fix from there.

@glennw
Copy link
Member

@glennw glennw commented Jan 23, 2018

I think this is fixed by #2307 - are you able to confirm?

@nc4rrillo
Copy link
Contributor Author

@nc4rrillo nc4rrillo commented Jan 23, 2018

Yes can confirm that fixed it.

@nc4rrillo nc4rrillo closed this Jan 23, 2018
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
4 participants
You can’t perform that action at this time.