Bug 38329 - [Qt] QtLauncher content view is ripped apart when scrolling.
Summary: [Qt] QtLauncher content view is ripped apart when scrolling.
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware Other
: P2 Critical
Assignee: QtWebKit Unassigned
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks: 35784
  Show dependency treegraph
 
Reported: 2010-04-29 07:51 PDT by Alexandra Santos
Modified: 2010-05-18 13:38 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandra Santos 2010-04-29 07:51:24 PDT
The QtLauncher content view gets ripped apart while scrolling; this when installed on a symbian device. 

Steps to reproduce:

1.- Install qt.sis, QtWebkit and Qt_launcher on a S60 (N97)Device.
2.- Launch Qt_Launcher.
3.- Load any page. (www.google, www.Cnn.com)

Actual Results:

The content view gets ripped apart. The content is unreadable.

Expected Result:

The content view must not be corrupted by scrolling.

NOTE:
When more than one page is loaded, it is displayed on top of the previous one. The screen is not cleared before loading the next page (As can be seen in the screen shot).
Comment 1 Timothy Lu 2010-04-30 06:24:33 PDT
this issue needs to be prioritized appropriately by the program.  Added to webkit 2.0 TOP list.
Comment 2 Timothy Lu 2010-04-30 06:26:43 PDT
(In reply to comment #1)
> this issue needs to be prioritized appropriately by the program.  Added to
> webkit 2.0 TOP list.

Added to https://bugs.webkit.org/show_bug.cgi?id=35784
Comment 3 Simon Hausmann 2010-04-30 07:21:08 PDT
Which qt.sis are you using? I thought this issue (garbage when scrolling) was fixed in Qt 4.6 a while ago.
Comment 4 Alexandra Santos 2010-04-30 07:31:10 PDT
QT 4.6.2 extracted from the following location: http://get.qt.nokia.com/qt/source/qt-symbian-opensource-4.6.2.exe
Comment 5 Janne Koskinen 2010-05-01 01:16:16 PDT
(In reply to comment #4)
> QT 4.6.2 extracted from the following location:
> http://get.qt.nokia.com/qt/source/qt-symbian-opensource-4.6.2.exe

I thought you guys where using latest source with S^4 and not 4.6.2 sis packages.. As Simon says this has already been fixed in Qt SHA 92465142116ed140b4323c4a8f5bc325c45cdccf .
See: http://bugreports.qt.nokia.com/browse/QTBUG-7286.

Please give that change a try.
Comment 6 Alexandra Santos 2010-05-03 13:03:43 PDT
Sure. Where can I find the 4.7 sis packages. Can you please point me to their location?
Comment 7 Janne Koskinen 2010-05-06 04:42:19 PDT
(In reply to comment #6)
> Sure. Where can I find the 4.7 sis packages. Can you please point me to their
> location?

You can try the newly released beta packages. Symbian sis packages from: http://get.qt.nokia.com/qt/symbian/4.7.0-beta1/
Comment 8 Alexandra Santos 2010-05-06 06:34:43 PDT
Those sis packages only contain Qt 4.6.2 I tried them just yesterday. The qt.sis file, while installing on the device,lets you know you are installing Qt 4.6.2
Comment 9 Kenneth Rohde Christiansen 2010-05-10 19:07:14 PDT
(In reply to comment #8)
> Those sis packages only contain Qt 4.6.2 I tried them just yesterday. The qt.sis file, while installing on the device,lets you know you are installing Qt 4.6.2

Can you confirm this Janne? or can you test again Alexandra?

It seems that this bug is already fixed, so it would be nice to confirm that and close it.
Comment 10 Simon Hausmann 2010-05-18 13:38:10 PDT
(In reply to comment #5)
> (In reply to comment #4)
> > QT 4.6.2 extracted from the following location:
> > http://get.qt.nokia.com/qt/source/qt-symbian-opensource-4.6.2.exe
> 
> I thought you guys where using latest source with S^4 and not 4.6.2 sis packages..

Janne, that does not apply to the developers working on N97, where Qt 4.6.2 is the current platform.

I'm trying to get hold of Jason to see if we can get a real Qt 4.6 snapshot for Symbian (with a proper installer).

Alexandra, I'll get back to you on this via email. In the meantime I'll close this bug, it's not a WebKit issue, merely a question of packaging.

In fact this bug is not present in the S^4 builds.