RESOLVED DUPLICATE of bug 31466 35660
[Qt] Cursor in QWebView/ WebKit (with setContentEditable true) does not show until lose/gain focus
https://bugs.webkit.org/show_bug.cgi?id=35660
Summary [Qt] Cursor in QWebView/ WebKit (with setContentEditable true) does not show ...
Tor Arne Vestbø
Reported 2010-03-03 03:43:08 PST
This bug report originated from issue QTBUG-5288 http://bugreports.qt.nokia.com/browse/QTBUG-5288 --- Description --- Version: 4.6.0-beta <p>Platform: Mac OS X <br/> Platform details: os x 10.5.4, mac pro 2X 2.66ghz, 7 gb ram safari 3.x </p> <p>Compilers: GCC <br/> Compiler details: default xcode compile </p> <p>Steps to reproduce / test case:</p> <p>Compile my included sample app </p> <p>1) Run sample app. <br/> 2) Since I make the content of the webview editable in code, the cursor should immediately start to "blink" telling the user that she can begin to type. </p> <p>Bug: </p> <p>The cursor in the webview should start to blink on launch but does not. </p> <p>Cursor does not show until you focus on another window in another app then return, or choose (in another app I wrote), the color picker, choose color, then dismissed it. </p> <p>In both those cases the cursor is then shown and starts to blink correctly. <br/> It should be noted that clicking anywhere in the webview now will also NOT show the cursor, (cursor does not update) as it should when a user clicks on a different part of the page for her to edit. </p> <p>More information:</p> <p>I have included a test app that recreates this and a quicktime movie that shows the cursor remaining hidden until the window with the webview loses focus and then regains it. </p> <p>In the quicktime movie you will see that as I click around the page, the cursor does not update or show. Then in the movie I click on the window to the left, which is an xcode window, and upon returning to the webview app, the cursor correctly display at the point of the mouse click. </p>
Attachments
Jocelyn Turcotte
Comment 1 2010-03-17 06:06:19 PDT
Could not reproduce. This bug was probably fixed in r50937. *** This bug has been marked as a duplicate of bug 31466 ***
Note You need to log in before you can comment on or make changes to this bug.