After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 758968 - faulty display of some elements
faulty display of some elements
Product: epiphany
Classification: Core
Component: Interface
3.18.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Reported: 2015-12-02 18:19 UTC by charlesaymard
Modified: 2016-01-28 23:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

accidentally uploaded wrong screenshot (8.33 KB, image/png)
2015-12-02 18:19 UTC, charlesaymard
example of faulty behaviour (4.05 KB, image/png)
2015-12-02 18:24 UTC, charlesaymard

Description charlesaymard 2015-12-02 18:19:44 UTC
Created attachment 316674 [details]
accidentally uploaded wrong screenshot

with some gtk themes (evopop, numix-frost-light), epiphany produces faulty displays of some page elements, like the buttons in the forms of the gnome bugzilla as shown in the screenshot. they are almost invisible until hovered over.
Comment 1 charlesaymard 2015-12-02 18:24:40 UTC
Created attachment 316675 [details]
example of faulty behaviour
Comment 2 Michael Catanzaro 2015-12-03 10:16:24 UTC
Thanks for taking the time to report this bug. Strange that one button should render properly, but not the button immediately below it.

I think this might be WebKit #151533, though I am not sure why it is an issue only for some themes and not others. I discovered that problem through code inspection, but I guess it could cause an issue like this in practice.
Comment 3 charlesaymard 2015-12-03 16:16:33 UTC
sorry that wasn't clear, but in the screenshot I was hovering over one of the buttons. I guess the screenshot tool removes the cursor from view.
Comment 4 Michael Catanzaro 2015-12-04 10:12:29 UTC
OK, I think that makes it even more likely to be WebKit #151533. :)
Comment 5 Michael Catanzaro 2016-01-22 15:14:48 UTC
I miiiight have fixed this in WebKit r193896 which has been backported to WebKitGTK+ 2.10.5; when you get 2.10.5, please say here if it's been fixed. Thanks!
Comment 6 charlesaymard 2016-01-28 18:28:30 UTC
I am not quite sure which packages would have to land for your commit to ship on my arch system.

At the moment, I have 
Name           : webkit2gtk
Version        : 2.10.6-1

Name           : webkitgtk
Version        : 2.4.9-5

Name           : webkitgtk2
Version        : 2.4.9-5

... and the behaviour hasn't changed.
Comment 7 Michael Catanzaro 2016-01-28 19:47:42 UTC
(In reply to charlesaymard from comment #6)
> I am not quite sure which packages would have to land for your commit to
> ship on my arch system.
> At the moment, I have 
> Name           : webkit2gtk
> Version        : 2.10.6-1

This one ^^^

The other three are obsolete, insecure packages.

So now we know my patch unfortunately did not fix this bug. Feel free to file a new bug on Since it doesn't happen with the default theme, though, I'm afraid it's not going to be a priority issue; sorry.
Comment 8 charlesaymard 2016-01-28 23:24:25 UTC
well, it's not that big an issue anyway.

about these webkit packages: one is required by gnucash, one by bijiben  evolution  gufw...