- From: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
- Date: Tue, 10 Aug 2010 09:29:43 -0300
- To: Rune Lillesveen <rune@opera.com>
- Cc: Kenneth Christiansen <kenneth.christiansen@openbossa.org>, www-style list <www-style@w3.org>
Well, yes. It is to avoid scaling and still provide web components (buttons etc) that have a clickable size. Basically most services such as GMail Mobile etc have lists and buttons optimized for the DPI of the iPhone, thus there is no scaling with a device-width of 320. If on the other hand you use a device-width of 480 the list items and buttons become small and harder to interact with so Android and Fennec (and us) considers the DPI difference (160 vs 240) and scales everything with a factor of 1.5. This results in us not having a pixel for each css pixel, using scaled images etc. This is something we want to avoid in order to make web apps look as native as possible, plus making them take advantage of our better screen. Kenneth > I understand, I'm just a bit unsure about the use cases. Is it to compensate > for missing/bad sub-pixel rendering? > > -- > Rune Lillesveen > Senior Core Developer / Architect > Opera Software ASA > > -- Kenneth Rohde Christiansen Technical Lead / Senior Software Engineer Qt Labs Americas, Nokia Technology Institute, INdT Phone +55 81 8895 6002 / E-mail kenneth.christiansen at openbossa.org http://codeposts.blogspot.com ﹆﹆﹆
Received on Tuesday, 10 August 2010 12:30:32 UTC