Bug 43187
| Summary: | [Qt] -webkit-text-fill-color / text-shadow problems | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jonathan Corwin <j> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ariya.hidayat, j, kling |
| Priority: | P2 | Keywords: | Qt, QtTriaged |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Jonathan Corwin
I'm not sure if I should be reporting this here, or in a PyQt bugtracker, or somewhere else. So apologies if I've picked the wrong one to try first.
I'm using PyQt 4.7.4 and working with a QWebView. I'm having a problem displaying the second example on this page:
http://webkit.org/blog/85/introducing-text-stroke/
Although I'm specifying a -webkit-text-fill-color and a text-shadow, neither are appearing. All I'm seeing is the webkit-text-stroke part of the rendering (i.e. thick red letters) with no shadow. I've tried replacing the transparent with yellow, just in case this was the cause, but with no joy.
Here is the python code
import sys
from PyQt4 import QtGui, QtWebKit
app = QtGui.QApplication(sys.argv)
main = QtGui.QMainWindow()
web = QtWebKit.QWebView(main)
main.setCentralWidget(web)
web.setHtml("<html><body><div style='font-size:64px; " \
"text-shadow: 5px 5px 5px black; " \
"-webkit-text-fill-color: yellow; " \
"-webkit-text-stroke:3px red'>" \
"Test</div></body></html>")
main.show()
sys.exit(app.exec_())
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jonathan Corwin
Note I get the same problem with both pyqt4 and pyside on Linux too.
Andreas Kling
This is slightly better on trunk. No shadows are drawn though, CC'ing Ariya who has been working on that lately.
Also, due to bug 44403 the stroke and the fill are not aligned properly.
Ariya Hidayat
Please follow https://bugs.webkit.org/show_bug.cgi?id=19728 for the shadow bug.
Jonathan Corwin
I notice that the alignment problem has been cherry picked for 2.1.
The shadow bug fix although committed, hasn't been cherry picked though, so will I have to wait for 2.2 for this?
I'm somewhat unfamiliar with the QtWebkit versioning/release schedule and struggled to find any information about it.
Andreas Kling
Closing as this is fixed in the next Qt release (QtWebKit 2.2 / Qt 4.8)