CLOSED FIXED 39066
[Qt] ContextMenu misplaced after window move
https://bugs.webkit.org/show_bug.cgi?id=39066
Summary [Qt] ContextMenu misplaced after window move
Antonio Gomes
Reported 2010-05-13 07:25:33 PDT
Created attachment 55973 [details] screenshot - look at the mouse position and when the contextmenu showed up Bug reproducible with QtLauncher, -graphicsbased option ON (webkit r59359) Steps to reproduce: 1) launch QtLauncher and trigger graphicsbased widget option. I do: $ run-launcher --qt -graphicsbased http://google.com ... but it can be done via Developer->GraphicsBased-> menu. 2) Move the window 3) Right click webcontent Expected: context menu shows up where you right click, or close enough to it Current: context menu shows up as if you have not changed the window position in step #2
Attachments
screenshot - look at the mouse position and when the contextmenu showed up (288.99 KB, image/png)
2010-05-13 07:25 PDT, Antonio Gomes
no flags
Antonio Gomes
Comment 1 2010-05-13 07:54:26 PDT
ok it will be fixed my patch in bug 39016 I am duping it *** This bug has been marked as a duplicate of bug 39016 ***
Antonio Gomes
Comment 2 2010-05-13 07:55:06 PDT
(In reply to comment #1) > ok it will be fixed my patch in bug 39016 it will be fixed BY patch ... it is not mine :)
Antonio Gomes
Comment 3 2010-05-13 07:56:22 PDT
(In reply to comment #2) > (In reply to comment #1) > > ok it will be fixed my patch in bug 39016 > > > it will be fixed BY patch ... it is not mine :) err, wrong bug. sorry for bug spamming
Simon Hausmann
Comment 4 2010-07-01 02:05:10 PDT
This is a regression against Qt 4.6: The context menu in QGraphicsWebView comes up at the wrong location.
Simon Hausmann
Comment 5 2010-07-02 00:51:36 PDT
It turns out that QGraphicsWebView's default code was fine and QtTestBrowser had a bug that Tor Arne fixed :)
Simon Hausmann
Comment 6 2010-07-02 00:52:47 PDT
Simon Hausmann
Comment 7 2010-07-02 01:47:06 PDT
Revision r62298 cherry-picked into qtwebkit-2.0 with commit a1dfe355a202b0de28e21b7f4e2942a60cb86347
Note You need to log in before you can comment on or make changes to this bug.