RESOLVED WORKSFORME 52285
HTML element is invisible when -webkit-transform and @font-face is set
https://bugs.webkit.org/show_bug.cgi?id=52285
Summary HTML element is invisible when -webkit-transform and @font-face is set
jon.ronnenberg
Reported 2011-01-12 02:49:58 PST
Chrome Version : 8.0.552.224 (Official Build 68599) URLs : http://gl-test.kathdreams.dk/culture.htm Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: OK Firefox 3.6: OK Steps to reproduce the problem? 1. Go to web site (http://gl-test.kathdreams.dk/culture.htm) 2. The h2 with text EXPLORE CULTURE is not visible. It's located in div.culture-cloud. Open the site in Safari or Firefox if you're having trouble finding the element. OR 1. download chrome.html and pioneerbrush-webfont.woff from here. 2. put pioneerbrush-webfont.woff in directory and name it fonts. 3. open chrome.html in Chrome I've attached the WOFF font as it might be a problem with transforming this particular WOFF file. The files is generated at fontsquirrel.com. What strikes me is that this works as intented in web-kit 533 (Safari 5.0) but not in web-kit 534 (Chrome 8). Cheers, Jon.
Attachments
reduced testcase (1.02 KB, text/html)
2011-01-12 02:50 PST, jon.ronnenberg
no flags
WOFF font that errors when rotated (117.98 KB, application/x-woff)
2011-01-12 03:34 PST, jon.ronnenberg
no flags
jon.ronnenberg
Comment 1 2011-01-12 02:50:49 PST
Created attachment 78670 [details] reduced testcase
jon.ronnenberg
Comment 2 2011-01-12 03:34:07 PST
Created attachment 78675 [details] WOFF font that errors when rotated
jon.ronnenberg
Comment 3 2011-01-12 03:34:27 PST
Simon Fraser (smfr)
Comment 4 2011-01-12 15:40:41 PST
I recall some other issues related to fonts not rendering when transformed. Memory hazy tho.
mitz
Comment 5 2011-01-12 15:47:14 PST
Is this specific to the Chromium Windows port or does it also happen with the Core Graphics-based Apple Windows port?
jon.ronnenberg
Comment 6 2011-01-17 04:26:48 PST
I just updated Chrome and the bug is still there: 8.0.552.237 (Official Build 70801) WebKit 534.10
jon.ronnenberg
Comment 7 2013-10-18 02:14:28 PDT
This bug has been fixed long ago. Unfortunately I don't know when but as following the timeline of comments in bug report #69342[1] on chromium, it appears fixed between late June 2011 - late February 2012. [1] https://code.google.com/p/chromium/issues/detail?id=69342
Note You need to log in before you can comment on or make changes to this bug.