Let's use this bug to track issues that need to be cherry-picked into the stable branch.
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.
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).
(In reply to comment #2) Uploaded to https://codereview.qt-project.org/52854
(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.
Bug-fixes now go to the 5.1 tree by default.