Bug 41137 - [Qt] QtWebKit -webkit-transform:translate3d fails on big DIV elements
Summary: [Qt] QtWebKit -webkit-transform:translate3d fails on big DIV elements
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on: 39691
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-24 01:14 PDT by Jonni Rainisto
Modified: 2012-02-23 18:07 PST (History)
7 users (show)

See Also:


Attachments
scrolling-testcase (367 bytes, text/html)
2010-06-24 01:14 PDT, Jonni Rainisto
no flags Details
patch enabling tiling on qtwebkit-2.1 (9.31 KB, patch)
2010-11-03 13:13 PDT, Ademar Reis
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jonni Rainisto 2010-06-24 01:14:27 PDT
Created attachment 59623 [details]
scrolling-testcase

Following scrolling-testcase.html file fails in Harmattan QtWebkit (red div turns black/disapears), and works on other platforms. Maybe QtWebKit OpenGL backend releated bug?
Comment 1 Diego Gonzalez 2010-07-21 08:28:29 PDT
Cannot reproduce this bug. Please check if it is still reproducible for you. If so try to reproduce it in a open platform.
Comment 2 Jonni Rainisto 2010-08-03 23:55:00 PDT
I can still reproduce this in Harmattan week31 release, so its still valid. Seems to be releated to QTWebKit opengl es2 backed, since div stays red if I do --graphicssystem=raster -software. Cannot reproduce on open platform (as I dont have any open hw which has gles2 backend).
Comment 3 Jonni Rainisto 2010-09-21 05:49:06 PDT
I can still reproduce this in Harmattan 38-8 QtWebKit using webwidgetrunner (red div disapears when you try to scroll the screen.
Comment 4 Suresh Voruganti 2010-10-26 11:28:15 PDT
Is this still reproducible? Can you give Meego Bugzilla ID?
Comment 5 Jonni Rainisto 2010-10-27 03:48:08 PDT
Yes, its still reproducible in 43-6. I created now also PMO bug in https://projects.maemo.org/bugzilla/show_bug.cgi?id=200690
Comment 6 Simon Hausmann 2010-10-29 07:32:31 PDT
Could this be a problem in the OpenGL paint engine?
Comment 7 Benjamin Poulain 2010-10-29 07:45:01 PDT
I think MAX_TEXTURE_SIZE is 2048 in this case. Textures bigger than that just fail.

This could be worked around by adding tiling for texture, either in WebKit or (better) in the graphics system.

I am tempted to just ignore that for the graphics view implementation and  do a proper fix for the texture mapper. How important is the bug?
Comment 8 Simon Hausmann 2010-10-29 08:09:14 PDT
(In reply to comment #7)
> How important is the bug?

It originates from a Maemo 6 bug (41137), triggered by the Qt Web Runtime.
Comment 9 Noam Rosenthal 2010-10-29 09:55:05 PDT
See https://bugs.webkit.org/show_bug.cgi?id=39691, I think it fixes it, though the patch needs to be re-applied etc.
Comment 10 Ademar Reis 2010-11-03 12:55:24 PDT
Please confirm if bug 39691 fixes it so that I can backport/cherry-pick the fix into qtwebkit-2.1
Comment 11 Suresh Voruganti 2010-11-03 13:02:47 PDT
I think we cannot test with out the fix of 39691 integrated to Qtwebkit 2.1

Let me know if we can test with out the fix being picked to 2.1?
Comment 12 Ademar Reis 2010-11-03 13:13:17 PDT
Created attachment 72856 [details]
patch enabling tiling on qtwebkit-2.1

Patch backported to qtwebkit-2.1. Please test, if it really solves the problem I'll push it into the official branch.
Comment 13 Jonni Rainisto 2010-11-04 05:03:42 PDT
applied the patch to harmattan 43-6, and tested it, but bug still appears. So this patch does not help.(In reply to comment #12)
> Created an attachment (id=72856) [details]
> patch enabling tiling on qtwebkit-2.1
> 
> Patch backported to qtwebkit-2.1. Please test, if it really solves the problem I'll push it into the official branch.

applied the patch to harmattan 43-6 qtwebkit sources, and tested it, but bug still appears. So this patch does not seem to help.
Comment 14 Noam Rosenthal 2010-11-04 10:45:56 PDT
Can we work around this for now (e.g. by using smaller layers in HTML) and postpone actual fix to 2.2?