summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/javascriptcore/JavaScriptCore/config.h
diff options
context:
space:
mode:
authorJason Barron <jbarron@trolltech.com>2010-02-19 11:05:44 (GMT)
committerJason Barron <jbarron@trolltech.com>2010-02-22 08:35:24 (GMT)
commit1eb303d4f14dfcffcca3f11cacca7a73f1e53342 (patch)
tree287405bcb6d29d40691aa9a1124e49394f97b37a /src/3rdparty/javascriptcore/JavaScriptCore/config.h
parent1a8fffa8cae5b4094adcd87bfc4cbc24599d7305 (diff)
downloadQt-1eb303d4f14dfcffcca3f11cacca7a73f1e53342.zip
Qt-1eb303d4f14dfcffcca3f11cacca7a73f1e53342.tar.gz
Qt-1eb303d4f14dfcffcca3f11cacca7a73f1e53342.tar.bz2
Don't use vgClear() for semi-transparent brushes.
If the brush is not totally opaque we should not use vgClear() at this point because vgClear() does not support blending. Instead it writes the values directly into the surface which clobbers any existing content. The bug exhibits itself when a child widget fills itself with any transparent color. Instead of blending with the parent widget's content, it writes the semi-transparent color directly to the surface, overwriting the parent content and leaving the surface in a somewhat undefined state because the alpha channel is not honoured unless Qt::WA_TranslucentBackground is set. Task-number: QTBUG-8007 Reviewed-by: Rhys Weatherley
Diffstat (limited to 'src/3rdparty/javascriptcore/JavaScriptCore/config.h')
0 files changed, 0 insertions, 0 deletions