summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src.scripttools.qscriptenginedebugger.cpp
diff options
context:
space:
mode:
authorSami Merilä <sami.merila@nokia.com>2009-11-16 08:26:33 (GMT)
committerJason McDonald <jason.mcdonald@nokia.com>2009-11-18 05:51:08 (GMT)
commit9adab252dceef088b0da3f5dd345772771339db8 (patch)
treebea6e7576d7f171ffdb58525929e2c26df70edfd /doc/src/snippets/code/src.scripttools.qscriptenginedebugger.cpp
parent2261f93f0489de02535a1957899fea41a020d1ee (diff)
downloadQt-9adab252dceef088b0da3f5dd345772771339db8.zip
Qt-9adab252dceef088b0da3f5dd345772771339db8.tar.gz
Qt-9adab252dceef088b0da3f5dd345772771339db8.tar.bz2
Define own palette for web-based widgets in QS60Style
It makes no sense to use the S60-theme based palette in web based widgets. Web pages do not generally show theme background, but their own (or by default white) which clashes badly with WindowText and Text that are set to work with theme background. Therefore, QWebView and QGraphicsWebView need to be set their own palette for texts in theme palette hash. This improves visibility of text in webkit when QS60Style is active. Task-number: QTBUG-4885 Reviewed-by: Janne Koskinen (cherry picked from commit 15384f3017978a3d552077c8400b018efcfd793c)
Diffstat (limited to 'doc/src/snippets/code/src.scripttools.qscriptenginedebugger.cpp')
0 files changed, 0 insertions, 0 deletions