On Tue, Oct 14, 2008 at 4:05 PM, Glen Murphy <[EMAIL PROTECTED]> wrote:
> Like Evan, I'm not at all a fan of changing the page layout for a > normal range of text size changes - sometimes I change font size > temporarily just to read something quickly, and having the page > relayout as a consequence would be pretty jarring. I think some of Evan's complaints are more correctly classified as bugs. On #chromium-dev roc noted that one such issue was an issue with the particular platform-specific image rescaling algorithm Firefox was using in one place. There are other bugs in our implementation. Bugs are real problems, but they don't necessarily mean full zoom is inherently worse (just like bugs in inline autocomplete don't mean inline autocomplete is inherently bad). As for full zoom being jarring, I'm not sure this isn't a matter of (a) familiarity and (b) a good implementation. Imagine, as a best case, a full zoom that can be done instantaneously, and then an algorithm that rapidly modifies the zoom level to do a "fast zoom in" (akin to the effect Google Maps tries for on zoom). I don't think such an implementation would be inherently more jarring, as both text zoom and full zoom can cause pages to need to relayout. Indeed, once people were accustomed to it, I suspect most would find it noticeably _less_ jarring. Zooming text on sites nearly always leads to strange artifacts or appearance glitches that full zoom doesn't necessarily cause. Summary: we shouldn't complain before we have a rock-solid implementation and can really step back and evaluate the two fairly. PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
