1663296 - black border around dialog windows webrender

Status: RESOLVED DUPLICATE of bug 1663003

(Core :: Graphics: WebRender, defect)

Description

[u658943]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0

Steps to reproduce:

• Install latest nightly (this issue first appeared for me a day or two ago but still appears on latest nightly as of the time of reporting this bug)
• Enable webrender

Actual results:

• All popup overlaying dialog windows like the "hamburger" menu, profile/account button, addon dialogs, etc. have a black border around them when clicked.
• This does not affect "standalone windows" (not sure if that's the right terminology) like the bookmarks properties editor for example

Expected results:

There should not have been a black border around the window

Comment 1

[u658943]

Attachment: 2020-09-06-000458_3840x2160_scrot.png

Picture of the issue

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 3

[Darkspirit]

Thanks for the report!
Do you start Nightly with MOZ_X11_EGL=1 env var and can this problem be fixed by not using this env var? Then it's a duplicate of bug 1663003.
Otherwise, If this is caused by enabling OpenGL/WebRender on i3wm/X11, it's a duplicate of long-time bug 1479135.
Because you mention it appeared two days ago you likely mean the first one.

Comment 4

[u658943]

(In reply to Darkspirit, Servo QA from comment #3)

Thanks for the report!
Do you start Nightly with MOZ_X11_EGL=1 env var and can this problem be fixed by not using this env var? Then it's a duplicate of bug 1663003.
Otherwise, If this is caused by enabling OpenGL/WebRender on i3wm/X11, it's a duplicate of long-time bug 1479135.
Because you mention it appeared two days ago you likely mean the first one.

*** This bug has been marked as a duplicate of bug 1663003 ***

Yes it does appear with MOZ_X11_EGL=1, and can be fixed by disabling that environment variable. Therefore it is a duplicate of bug 1663003.
Thank you.