On Tue, Nov 18, 2008 at 12:13 PM, Amanda Walker <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 18, 2008 at 2:05 PM, Brett Wilson <[EMAIL PROTECTED]> wrote: >> This is not platform-specific on any other architecture, and it >> doesn't need to be. The difference is that font and form control >> rendering have to be native for us to look correct. This is not the >> case for images or any other part of GraphicsContext. > > But font and form control drawing *use* GraphicsContext, which is what > prompted turning on PLATFORM(CG) in the first place. We can turn off > PLATFORM(CG), which resolves the type mismatches for images--but also > means forking FontMac, FontMacATSUI, and so on (a total of a dozen or > so files, last time I tried it) or upstream a patch that replaces a > lot of code like "CGContextRef cgContext = context->platformContext()" > with platform-specific macro (a type of patch that WebKit has been > resistant to so far, from what I've seen).
That's what I was saying may or may not be worth it, and what the decision really comes down to. Brett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
