Slashdot Mirror

← Back to Stories (view on slashdot.org)

Next in Browser Development, High DPI Websites?

Posted by ryuzaki0 on from the more-dots dept.

Joost de Valk writes "In a post at the WebKit blog, Dave Hyatt raises interesting points about the future of web development and browsers. He says, that with screens getting more and more pixels, it is imperative website design takes the next step: High DPI Website rendering. This could mean that a CSS pixel (px) is rendered as a 2x2 pixelblock. In the article he also mentions WebKit will be providing possibilities to use SVG for all kinds of purposes, like backgrounds. He calls upon other browser developers to take part in the discussion so that 'concrete standards in this area can be hammered out.'"

4 of 447 comments (clear)

  1. I agree...something fundamentally wrong with this. by Joce640k · · Score: 4, Interesting
    To make this work you need more dots per inch on the monitor, not just "higher resolution". Current "high resolution" screens are bigger, not more densely pixelled.

    Without changing the dot pitch 2x rendering would make the ducument twice as wide, and that's going to make things worse, not better.

    FWIW, I currently see no industry interest in higher pixel density screens, in fact I see the total opposite. Most 19" screens on the market have the same number of pixels as 17" screens. This maybe good for filling a gamer's field of view but documents are much less readable on a 19" LCD than on a 17" one. The only big change which might happen in the near future is that 19" monitors catch up with 17" ones in terms of pixel density.

    --
    No sig today...
  2. Re:A couple of things... by featherstorm · · Score: 3, Interesting

    The default setting is 72 dpi for Macs and 96 dpi for Windows, not vice versa. Actually, neither is true for most of the displays available nowadays. Put a ruler to your screen and measure the pixels to an inch. My 23" Apple Cinema Display has 98 dpi, the PowerBook it's attached to 106 dpi.
    In mozillaoid browsers you would therefore enter this into your user.js:

    user_pref("browser.display.screen_resolution", 98);

  3. It'll reach a point where you can't by Sycraft-fu · · Score: 4, Interesting

    Let's say you have one of the ultra high rez wquxga monitors that's 3840x2400 in 24" (those are real by the way). At a size developed for normal monitors, you wouldn't be able to see anything. One pixel is just not visible with the naked eye. It's the kind of dsiplay you can literally hold a magnifying glass to to get more detail.

    However I think they are wrong in that web standards need to deal with this. What should deal with it, and what will allegedly deal with it, is OSes. As OSes gain hardware acceleration of their desktops, real resolution independance becomes easy to achieve. You know the rez of the monitor and its' size (monitors report how large they are). Then you just need the user to specify zoom level. At 100%, a 12 point font is rendered as 12 points, at 50%, it's rendered as 6 points. Graphics could likewise be scaled.

    Vista is allegedly supposed to be able to do this, though I'm not sure it'll actually make it in for release. Either way, I suspect it's something comming for all OSes sooner rather than later.

  4. What's new? by Lobais · · Score: 3, Interesting

    Opera has for a long time supported page "zoom", that allows you to make things bigger, without messing up the layout. IE7 will, as far as I know, have this feature too.

    Why all this new standards/browsers/websites talk?