1655330 - Full page blurred background image produces blurred page edges after closing developer tools

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect, P3)

Description

[Lukas Wochner]

Attachment: test.html

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0

Steps to reproduce:

1. Create HTML page with fixed fullscreen div element with oveflow: hidden;
2. Create pseudo "after" or "before" absolute block element as a child and strech it to full parent size.
3. Give the pseudo element a background image which covers the hole element dimensions (e.g. background-size: cover;)
4. Add a blur filter with "filter: blur(20px)" to the pseudo element.
5. Scale the pseudo element up to "transform: scale(1.2)" to hide blurred image edges. (childs grows over parents boundaries to hide blurred edges)
6. Open and close developer tools (e.g. browser console)

Actual results:

Blurred edges appearing on browsers window/page boundaries. Even adding negative margins to move the element and the blurred background edges outside of viewport doesn't help.

-Reload does not fix the problem.
-The only solution is to close the file and reopen it in firefox

• Can't reproduce the problem in chromium

Expected results:

Blurred edges of background image are moves outside of parents boundaries so they are hidden (overflow: hidden to prevent scolling) from the user.

Comment 1

[Lukas Wochner]

Attachment: Page before opening dev tools

Comment 2

[Lukas Wochner]

Attachment: After opened and closed dev tools

Comment 3

[Clara Guerrero ( Need Info Brindusa Tot Please)]

Hi Lukas,

Can you try this on the latest version of nightly? You can download it from here: https://nightly.mozilla.org/
Can you provide the test link to replicate on my end?

I will move this over to a component so developers can take a look over it. If is not the correct component please feel free to change it to an appropriate one.

Thanks for the report.

Best regards, Clara.

Comment 4

[Darkspirit]

Should this just be duped to bug 1654442 and wontfixed for release?

Gnome Xwayland, Debian Testing, 2560x1440@60Hz, Intel HD Graphics 630 (KBL GT2)
STR: Press F12 twice. Nothing else.
good: With last good, first good, Nightly and Chromium, edges only become such bright if you drastically reduce window size.
bad: comment 2.
mozregression --good 77 --bad 79 --pref gfx.webrender.all:true -a https://bugzilla.mozilla.org/attachment.cgi?id=9166149

6:35.00 INFO: Last good revision: 91130843124c672198776445bf10bd12b0ab2595
6:35.00 INFO: First bad revision: 22227ba866f7e720947856905d092242cfc8f8f0
6:35.00 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=91130843124c672198776445bf10bd12b0ab2595&tochange=22227ba866f7e720947856905d092242cfc8f8f0

22227ba866f7e720947856905d092242cfc8f8f0 Glenn Watson — Bug 1636320 - Part 2 - Remove spatial node from clip interning. r=Bert
5313bc3ed301224926fcf1c116e5c9d1d983b5de Glenn Watson — Bug 1636320 - Part 1 - Separate internal clip chains from public API. r=Bert

mozregression --find-fix --bad 79 --good 2020-07-29 --pref gfx.webrender.all:true -a https://bugzilla.mozilla.org/attachment.cgi?id=9166149

7:50.01 INFO: First good revision: 72f4a4d07192ef6dc64f8d3a8fdfe6124db14ae7
7:50.01 INFO: Last bad revision: 99616c0729ec7a21dc0c1bde523c9779b71a0af9
7:50.01 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=99616c0729ec7a21dc0c1bde523c9779b71a0af9&tochange=72f4a4d07192ef6dc64f8d3a8fdfe6124db14ae7

72f4a4d07192ef6dc64f8d3a8fdfe6124db14ae7 Glenn Watson — Bug 1654442 - Add primitives to picture cache slices earlier during scene building r=nical

Comment 5

[Lukas Wochner]

(In reply to Clara Guerrero from comment #3)

Hi Lukas,

Can you try this on the latest version of nightly? You can download it from here: https://nightly.mozilla.org/
Can you provide the test link to replicate on my end?

I will move this over to a component so developers can take a look over it. If is not the correct component please feel free to change it to an appropriate one.

Thanks for the report.

Best regards, Clara.

Hi Clara,
I tried it on the latest nightly version and the bug disappeared.

Best regards, Lukas

Comment 6

[Glenn Watson [:gw]]

It's somewhat surprising that it was fixed by the patch noted above, as that should have been strictly a refactor, not causing any functional changes.

It'd be good to investigate why that did change behavior at some point, though I probably won't have time to this week. So yea, I guess we dupe this and wontfix since it's working OK in nightly?

Comment 7

[Kim Moir [:kmoir] ET]

:ktaleman Triaging as REO for 79, can you set a priority and severity for this bug?