When QtMobility is available, enable orientation by default.
Created attachment 76114 [details] patch Enable orientation flag by default if QtMobility is available.
The commit-queue encountered the following flaky tests while processing attachment 76114 [details]: inspector/debugger-expand-scope.html Please file bugs against the tests. These tests were authored by yurys@chromium.org. The commit-queue is continuing to process your patch.
Comment on attachment 76114 [details] patch Clearing flags on attachment: 76114 Committed r73687: <http://trac.webkit.org/changeset/73687>
All reviewed patches have been landed. Closing bug.
(In reply to comment #3) > Committed r73687: <http://trac.webkit.org/changeset/73687> I have some problem with this patch: (1) This kind of patches always break the incremental build, because adding or removing a define doesn't trigger rebuilding files. See the following bugs for details: https://bugs.webkit.org/show_bug.cgi?id=42027 (comment25,26) https://bugs.webkit.org/show_bug.cgi?id=38054#c25 Unfortunately there isn't a correct way to fix this bug. Plese ping me next time before landing a similar patch and I will force a clean rebuild on buildbots. (2) Please run layout tests before landing a patch not to break any test. Unfortunately I had to do it after landing: http://trac.webkit.org/changeset/73693. (3) There was a similar previously r+ -ed, but not landed patch to fix layout tests and enable DeviceOrientation: https://bugs.webkit.org/show_bug.cgi?id=47490
Thanks and sorry for the inconvenience.
Fix required for Qtwebkit 2.1/2.2. Developer has also attached the back ported version of the patch for Qtwebkit 2.1/2.2
Qi, do we need back ported version of patch for integrating Qtwebkit 2.1/2.2 ?
I already created in back ported version in bug 50685, I means I used one patch to cover 50685 and 50781.
(In reply to comment #9) > I already created in back ported version in bug 50685, I means I used one patch to cover 50685 and 50781. Please avoid doing that when backporting patches. We try to keep the same patches (same description, changelog and bug references) on the stabilization branches so that people (and tools) can easily find out what is part of a release. That said, don't worry about this particular patch, I'll split it myself based on the patches from trunk (the conflicts are easy to solve).
Sorry for inconvenience.
Revision r73687 cherry-picked into qtwebkit-2.2 with commit 3570f27 <http://gitorious.org/webkit/qtwebkit/commit/3570f27>
Revision r73693 cherry-picked into qtwebkit-2.2 with commit c08c19f <http://gitorious.org/webkit/qtwebkit/commit/c08c19f> (fix for tests, patch from Ossy, see c#5)
Created attachment 92759 [details] Fix LayoutTests for the 2.1.x branch Cherry-picking revision r73693 into qtwebkit-2.1.x (formerly known as qtwebkit-2.2) with commit c08c19f was too ambitious as this commit assumes that DeviceMotion is supported (which is the case on trunk but not on qtwebkit-2.1.x). Attached patch fixes the test expectations for qtwebkit-2.1.x. Ademar, can you please commit it to 2.1.x ?