This master bug tracks bugs which we would like to include in the qtwebkit-2.2 release but which are not considered critical and therefore won't block the release.
For release critical bugs use bug 50925
As this is a nice to have, shouldn't it be a P2 instead of P1?
(In reply to comment #1)
> As this is a nice to have, shouldn't it be a P2 instead of P1?
Makes sense... done
(never paid much attention to it, but I assume it may be useful to somebody)
The version previously known as QtWebKit-2.2 will actually be an update to QtWebKit-2.1 (probably 2.1.1). Changing summaries and references to reflect this.
Removing 51196 ==> Not a hard-requirement for 2.1.x and patch is not trivial (several conflicts).
Joel Parks, do you still want to provide a backport fix for bug 20382? It seems the issue is now fixed in trunk, but unclear where according to original report.
[Qt] ImageDiff sometimes hangs
It would be nice if you can cherry-pick http://trac.webkit.org/changeset/78840 to 2.1 and 2.1.x brances too.
It isn't critical, but very useful tool fix. It can
help me to make these buildbots green again.
Since 2.1.x is about to be released, this bug should be closed and relevant bugs moved to Bug 50925.
Closing this bug, as no nice-to-have bugs will be added anymore. If it's critical, please add it to Bug 50925