I just got the nightly of webkit r41242 and tested it in my website and when I did all the text on the site was replaced by random text and characters with a ton of errors in the logs saying "2/26/09 9:38:08 PM Safari[728] GCGetGlyphIdealMetrics failed: error 1." Here is a pic of the page is you want: http://img9.imageshack.us/img9/1084/picture1glb.png
Wow, that's a nasty one!
<rdar://problem/6629728>
The problem appears to be specific to the version of Geneva used on the webpage.
I'm not sure that this is a regression any more as I realised that I wasn't testing what I thought I was testing.
It's probably a violation of the license of the font to be redistributing it like this. The font even says © Apple.
(In reply to comment #5) > It's probably a violation of the license of the font to be redistributing it > like this. The font even says © Apple. I never really thought of it as a violation, I think I just got the font from the internet somewhere. But even if it is a violoation, it seems there is still a bug here.
Created attachment 28072 [details] Console output of GCGetGlyphIdealMetrics errors
Created attachment 28073 [details] Reduction Here's a simple reduction using the copy of the font on his page.
So has anyone made any progress on this? BTW, This font works perfectly in Gecko 1.9.1.
Dan is probably the one to fix this bug, but since it is a regression I could try to find the point of regression.
Do we have any evidence that this is a regression? The only comment about that is from me saying I don't think it is.
(In reply to comment #11) > Do we have any evidence that this is a regression? The only comment about that > is from me saying I don't think it is. Both the site and my reduction work fine for me in Safari 3.2 Do they not work for you?
(In reply to comment #12) > (In reply to comment #11) > > Do we have any evidence that this is a regression? The only comment about that > > is from me saying I don't think it is. > > Both the site and my reduction work fine for me in Safari 3.2 Do they not work > for you? > It all works fine for me in Safari 3.2.
Does anyone know what component this bug is related to so we are able to take it out of "New Bugs"?
There's no problem with it being in the New Bugs component.
(In reply to comment #15) > There's no problem with it being in the New Bugs component. > True, its just not very specific.
The bug no longer occurs (tested with Safari 7.0.6 on OS X 10.9.4).