M5 apprunner, GTK+ 1.2.0, xfstt 0.9.10 used for TrueType font services. When I mouse over the "Together" link on this page, the text does turn white per the A:hover CSS rule but the baseline of the "g" stays red. No other characters with descenders on this page exhibits this bug.

Tried on both WIN32 and Linux builds and it works correctly. The base of the "g" is turned completely white on a mouseover. Ramiro, I am reassinging this to you. My guess is that it is a problem with using the TrueType font services on Linux. Maybe we are not returning the correct font information from nsFontMetricsGTK for GetMaxDescent when a TrueType font is used.

Tried on both WIN32 and Linux builds and it works correctly. The base of the "g" is turned completely white on a mouseover. Ramiro, I am reassinging this to you. My guess is that it is a problem with using the TrueType font services on Linux. Maybe we are not returning the correct font information from nsFontMetricsGTK for GetMaxDescent when a TrueType font is used.

Tried on both WIN32 and Linux builds and it works correctly. The base of the "g" is turned completely white on a mouseover. Ramiro, I am reassinging this to you. My guess is that it is a problem with using the TrueType font services on Linux. Maybe we are not returning the correct font information from nsFontMetricsGTK for GetMaxDescent when a TrueType font is used.

I just tried this with xfstt 0.9.99-1 and the win98 fonts and i dont see the problem.

Just upgraded to xfstt 0.9.99, and here's the new behaviour of the bug. I'm using M5 apprunner. Go to http://www.webstandards.org/ and mouse over "Together" while document is loading (progress bar twirls). The link repaints correctly, but there is a split-second delay between everything *but* the descender repainting, and the descender repainting. Once loading is complete (no progress bar), the descender does not change color. If these hints don't manifest it for anyone else, please resolve this bug as WORKSFORME.

As of M8, works fine. Don't ask me why.

With the Sept 2 build, the problem has been fixed.