On Jun 15, 2012, at 8:02 AM, Jean-Daniel Dupas wrote: > Because Chrome is not a "Normal" app, and it does not just use standard API > for rendering.
To be precise: Chrome draws web page contents into offscreen pixmaps and then copies those to the screen. (This is for security: the drawing is done by WebKit in sandboxed renderer processes, using shared-memory buffers.) The problem is that it bases the pixmap dimensions on the logical size (in view coordinates) of the window, not the actual size in device pixels. BTW, this seems to have been fixed in the latest developer-channel builds of Chrome, since I just got my RetinaBook today and Chrome doesn't look jaggy to me. Presumably the fix will be ported into the stable releases too. (I'm sure Safari at one point had the same issue since it also uses sandboxed renderers, but of course they fixed that in time before the product release, just like the other retina-savvy Apple apps.) —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
