RESOLVED FIXED 201407
[GTK] Tooltips from previous about:overview page loads appear improperly on future pages
https://bugs.webkit.org/show_bug.cgi?id=201407
Summary [GTK] Tooltips from previous about:overview page loads appear improperly on f...
Michael Catanzaro
Reported 2019-09-02 15:14:20 PDT
Look at the attached screenshot. A tooltip improperly appears whenever hovering the mouse pointer over any portion of the page. The tooltip corresponds to the about:overview page, which was the last website displayed in the view before the current website. It shouldn't be showing up here. I think it's a regression from 2.24, but I'm not certain because I can't reproduce it on demand. It happens often, but not when I want to reproduce it. It must be a WebKit bug though, because the WebKitWebView does not have its tooltip-text property set. So the tooltip is being displayed by WebKit, not by GTK.
Attachments
Bugzilla test - this attachment not relevant to the bug (1.50 KB, text/plain)
2019-09-02 15:17 PDT, Michael Catanzaro
no flags
Screenshot (184.16 KB, image/png)
2019-09-02 15:20 PDT, Michael Catanzaro
no flags
test (184.16 KB, image/png)
2019-09-02 15:22 PDT, Michael Catanzaro
no flags
Michael Catanzaro
Comment 1 2019-09-02 15:17:40 PDT Comment hidden (obsolete)
Michael Catanzaro
Comment 2 2019-09-02 15:20:03 PDT
Created attachment 377861 [details] Screenshot
Michael Catanzaro
Comment 3 2019-09-02 15:22:16 PDT Comment hidden (obsolete)
Cédric Bellegarde
Comment 4 2019-09-10 13:28:39 PDT
For me was not happening in 2.24 but with 2.25.92, it happens all the time. Eolie and Epiphany: https://youtu.be/-1f6AKixP1U
Cédric Bellegarde
Comment 5 2019-09-10 13:31:57 PDT
Easy to reproduce, just let tooltip popups and click on overview preview.
Adrian Perez
Comment 6 2020-07-23 16:13:49 PDT
I think this has been fixed at some point, I cannot reproduce it anymore (tried trunk and 2.28.3, the issue is gone in both.) Can anyone else still reproduce this? If not, I think we can close the bug.
Michael Catanzaro
Comment 7 2020-07-24 07:50:14 PDT
This is definitely fixed, yes.
Note You need to log in before you can comment on or make changes to this bug.