[Webkit-unassigned] [Bug 24584] Translucent text rendering on Chromium is broken

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 13 13:43:52 PDT 2009


------- Comment #5 from senorblanco at chromium.org  2009-03-13 13:43 PDT -------
(In reply to comment #4)
> composite() is OK.  It's not particularly specific (you'd still have to read
> the composite() function to guess at what it did).  It seems it would also make
> sense to ASSERT if possible that we'd already composited.  We should probably
> be clearing m_savedOnDrawContext after restore now that this is a free
> function.  composite() (or whatever you call it) should also be a private
> function, since no one should call it except for the destructor.

Actually, no.  This work isn't done in the destructor any more, since that was
what was causing the problem (it's too late).  It's called explicitly by
FontChromiumWin, so it needs to be public.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list