WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 27296
Bug 29574
[Qt] Style changes to webpage by javascript triggered by signals doe sn't take effect immediately
https://bugs.webkit.org/show_bug.cgi?id=29574
Summary
[Qt] Style changes to webpage by javascript triggered by signals doe sn't tak...
Tor Arne Vestbø
Reported
2009-09-21 08:37:45 PDT
This bug report originated from Nokia internal issue QT-1807 --- Comments --- Product Qt Function webkit Version 4.5.0 Platform Linux Platform details Using 4.5.0-0ubuntu4.1 as supplied by Ubuntu. Also tested on 4.5.2 with a recent webkit svn revision by Chaz6 in #qtwebkit Compilers GCC Compiler details Subject Style changes to webpage by javascript triggered by signals doesn't take effect immediately Steps to reproduce / test case 1. Create a QWebView and add a QObject to its javascript. 2. Connect a javascript function to a signal on QObject. 3. Emit the signal, and have the handler makes a change to the document's background color. Results: The changes to the page will not take effect until one of the following: 1) Hover over the widget with the mouse cursor. 2) Make a dom manipulation to the document (before or after the css change). 3) Cause an alert. More information The test-case has a button and a webview. clicking on the button prints a message to stdout (via the javascript object) and should cause the webview to turn blue. It doesn't turn blue until hovering over it with the mouse. In the source code, the handler function has two dom manipulations before and after the css change. Uncommenting any of them will cause the color to change immediately without a mouse hover. I filed this bug in webkit's bugzilla.
Attachments
Add attachment
proposed patch, testcase, etc.
Tor Arne Vestbø
Comment 1
2009-09-21 08:38:15 PDT
*** This bug has been marked as a duplicate of
bug 27296
***
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug