|Summary:||[Qt][Meta] Tracker bug for fixes for Qt 5.0.x stable branch|
|Product:||WebKit||Reporter:||Simon Hausmann <hausmann>|
|Component:||WebKit Qt||Assignee:||Simon Hausmann <hausmann>|
|Severity:||Normal||CC:||abecsi, allan.jensen, iacobcatalin, jturcotte, michael.bruning|
|Version:||528+ (Nightly build)|
|Bug Depends on:||101867, 103146, 103452, 103865, 103901, 104134, 104364, 104436, 104525, 104574, 104909, 105014, 105016, 105087, 105096, 105127, 105818, 106018, 106699, 106777, 107031, 107449, 107547, 108165, 108213, 108815, 110149, 112239|
Description Simon Hausmann 2012-11-30 07:34:08 PST
Let's use this bug to track issues that need to be cherry-picked into the stable branch.
Comment 1 Michael Brüning 2012-12-03 05:38:10 PST
Kenneth pointed me to https://bugs.webkit.org/show_bug.cgi?id=103452, which affects Qt as well and I think it's important to have working fixed elements.
Comment 2 Catalin Iacob 2013-04-03 01:08:26 PDT
I'd like the fix for https://bugs.webkit.org/show_bug.cgi?id=108165 to be cherry-picked to the 5.0.x branch so that it arrives in 5.0.2. It's one line pretty obviously correct fix for a bug introduced by a refactoring. Qt 5.0 happened to get the WebKit version after the refactoring so it also got the bug. The consequence of this bug for me is that after I push an artificial MouseButtonPress QMouseEvent to a QWebPage, I can't rely on the event.isAccepted() value to know whether the event was handled by JS or not. This works for MouseButtonRelease which is not affected by #108165. I can't add #108165 to the Depends on field of this bug myself (I suppose I don't have enough privileges).
Comment 3 Jocelyn Turcotte 2013-04-03 07:09:31 PDT
(In reply to comment #2) Uploaded to https://codereview.qt-project.org/52854
Comment 4 Jocelyn Turcotte 2013-04-05 04:06:48 PDT
(In reply to comment #2) > I'd like the fix for https://bugs.webkit.org/show_bug.cgi?id=108165 to be cherry-picked to the 5.0.x branch so that it arrives in 5.0.2. Hi Catalin, unfortunately the change is a bit too late since 5.0.2 is scheduled very soon. Thanks for tracking it down in any case, the change has been cherry-picked to the 5.1 branch.
Comment 5 Allan Sandfeld Jensen 2013-09-23 08:19:16 PDT
Bug-fixes now go to the 5.1 tree by default.