Bug 35106

Summary: [Qt] Bug with QWebView::setPage() if QWebPage in editable mode.
Product: WebKit Reporter: NOX <nox>
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Major CC: benjamin, cmarcelo, kent.hansen, nox, tonikitoo
Priority: P5 Keywords: Qt, QtTriaged
Version: 420+   
Hardware: All   
OS: All   
Attachments:
Description Flags
Simple app to reproduce QWebView::setPage() bug
none
Another simple app to test bug none

NOX
Reported 2010-02-18 10:14:22 PST
Created attachment 49028 [details] Simple app to reproduce QWebView::setPage() bug Bug with QWebView::setPage() if QWebPage in editable mode. After writing in one tab and switching to another Text Caret has disapear. Try app in attachment. To reproduce bug: 1. Write some text to second tab 2. Then switch to first 3. Switch to second 4. Try to write in first Windows XP SP3, qt 4.6.1, MS compiller (with QtCreator 1.31)
Attachments
Simple app to reproduce QWebView::setPage() bug (1.44 KB, application/zip)
2010-02-18 10:14 PST, NOX
no flags
Another simple app to test bug (11.17 KB, application/zip)
2010-02-26 07:07 PST, NOX
no flags
NOX
Comment 1 2010-02-26 07:07:34 PST
Created attachment 49581 [details] Another simple app to test bug
Benjamin Poulain
Comment 2 2010-03-05 14:47:30 PST
I can reproduce it with trunk. This is a low priority bug. What you can do is a QStackedWidget with several QWebView. When the tab change, you just change the current QWebView. This will keep the state (scroll position, carret position, etc) when you switch tab, which is the behavior usually expected by users.
Jocelyn Turcotte
Comment 3 2014-02-03 03:16:11 PST
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.
Note You need to log in before you can comment on or make changes to this bug.