Bug 50925 – [Qt] Tracker bug for the QtWebKit 2.1.x release (critical)

• Status: RESOLVED
• Resolution: FIXED
• Component: New Bugs

[Ademar Reis]

This master bug tracks all bugs that prevent us from releasing QtWebKit 2.2.

Non critical bugs should be added to the "nice-to-have" tracker bug (see next comment for a reference)

[Ademar Reis]

For non critical bugs, use bug 50926

[Ademar Reis]

Since QtWebKit-2.2 will be based on QtWebKit-2.1 (which has not been released yet), adding bug 39121 to the "depends on" list.

[Ademar Reis]

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.

[Joel Parks]

51208, 45722 needed for BR-7405 (instead of 55380)

[Joel Parks]

Fabrizio Machado commented on BR-7405:
--------------------------------------

After some digging, I can see the fix code is simply not in the latest 2.1.x, although the bug report says it was picked up:
https://bugs.webkit.org/show_bug.cgi?id=51208

We need r74220 from trunk, basically.

To be clear, for 2.1.x, we need to mimic trunk logic and unconditionally set the "Antialiasing" render hint in the GraphicsContextPlatformPrivate constructor:

GraphicsContextPlatformPrivate::GraphicsContextPlatformPrivate(QPainter* p) { ...
painter->setRenderHint(QPainter::Antialiasing, true);
}

[Deepa Shah]

https://bugs.webkit.org/show_bug.cgi?id=57075 is needed for BR-7551.

[Joel Parks]

56752 needed for BR-7461, BR-7445

[Ademar Reis]

Bug 57075 is a refactoring (as the title says), and should not be included in a minor version of QtWebKit... Is there a (very) good reason for this?

[Deepa Shah]

http://trac.webkit.org/changeset/69064 is needed for BR-7275.

[Alexis Menard (darktears)]

I don't see any point to let that bug open no? It's released now and all the bugs are closed. Ademar?

[Ademar Reis]

(In reply to comment #10)
> I don't see any point to let that bug open no? It's released now and all the bugs are closed. Ademar?

This is being used to track a potential 2.1.2 release. Let's keep it that way until we're done with these 2.1.x releases for specific devices.

[Ademar Reis]

There are no plans for 2.1.2 anymore, so closing this bug. Critical issues for the 2.1 branch should be added to the maintenance bug: Bug 63647

Also note that the 2.1.x branch is no more. It has been merged into 2.1, which is the consolidated branch for any potential future 2.1 release (tags and SHA1's have been preserved). The only reason for the 2.1.x branch was that work started in 2.1.1 before the release of 2.1.0 -- why? that's a long story :-)