News for hackers. Stuff that matters.
Re:We're in an icon-sharpness limbo by alexchamberlain on Sunday March 25, 2012 @03:23PM (#3753510)
We need a multi-resolution image format and/or support for browsers to dictate to the server what size they want.
Re:We're in an icon-sharpness limbo by ars on Sunday March 25, 2012 @03:25PM (#3753515)
There is a workgroup working on it: http://www.w3.org/community/respimg/

Some of the options: https://etherpad.mozilla.org/responsive-assets

Re:We're in an icon-sharpness limbo by alexchamberlain on Sunday March 25, 2012 @03:48PM (#3753585)
We need to send the dimensions with the image request. It's the only way.
Re:We're in an icon-sharpness limbo by pornel on Sunday March 25, 2012 @05:32PM (#3753891)
There are many factors beyond screen size that could be involved in selection of image DPI: bandwidth availability and cost, screen density and current zoom level, amount of free memory available, hardware limitations (like iPad's max 1024px bitmaps).

Sending all these factors to the server would be problematic, so IMHO it's better if page declaratively specifies what sizes are available and lets UA pick one (so my UA doesn't need to tell every server when I'm out of my bandwidth allowance and hope server acts as expected).

Re:We're in an icon-sharpness limbo by alexchamberlain on Monday March 26, 2012 @02:32AM (#3755364)
I disagree to some extent. Given DPI, screen density and zoom level, the CSS etc should dictate the pixel width/height which can be sent to the server to obtain the correct version.
Re:We're in an icon-sharpness limbo by daxelrod on Sunday March 25, 2012 @05:27PM (#3753875)
This is actually an ingenious idea. HTTP content negotiation seems like it would come close to doing this well.
Re:We're in an icon-sharpness limbo by ricardobeat on Sunday March 25, 2012 @03:32PM (#3753534)
We can already do that with media queries, it doesn't solve the vector anti-alias/detail problem.
Re:We're in an icon-sharpness limbo by WiseWeasel on Sunday March 25, 2012 @03:43PM (#3753572)
Actually, the media queries only work for CSS image properties, like background-image, not for HTML img elements. We do need something equivalent to HTML5's handling of video, where you just stick a bunch of different paths to various formats in the video tag, and the browser selects the best one. Something like that for images would be nice; now we have to resort to jQuery hacks.
Re:We're in an icon-sharpness limbo by alexchamberlain on Sunday March 25, 2012 @03:49PM (#3753591)
Disagree, we want the same asset, just a different size.
Re:We're in an icon-sharpness limbo by WiseWeasel on Sunday March 25, 2012 @03:58PM (#3753620)
If it contains all the different possible resolutions you might need, that one asset would be larger than the one of several assets appropriate for the device in question, so you'd be wasting everyone's bandwidth and needlessly degrading your site's performance.
Re:We're in an icon-sharpness limbo by ricardobeat on Monday March 26, 2012 @10:35AM (#3756851)
Being icons, the difference is negligible. You can also show different images using pseudo elements, in any case you don't usually use image tags for icons, it's an image replacement, background or pseudo element.
Re:We're in an icon-sharpness limbo by alexchamberlain on Sunday March 25, 2012 @04:16PM (#3753689)
I'm not saying we should send every version of that asset... only the one we need.
Re:We're in an icon-sharpness limbo by WiseWeasel on Sunday March 25, 2012 @04:24PM (#3753715)
What? You want a single asset that works at all resolutions, but you don't send the whole thing? Please elaborate.

[edit] I think you might be looking for a single vector design that looks good at all resolutions. Such a beast does not exist due to the low-resolution nature of most displays with which anti-aliasing can only help so much. There is no way to get around different designs for different rendered sizes if you want it to look good. You always design for a target rendered size. SVG just helps you serve 1x (most displays) and 2x (retina displays) resolution optimally with the same file. [/edit]

Re:We're in an icon-sharpness limbo by alexchamberlain on Sunday March 25, 2012 @04:59PM (#3753799)
Not necessarily vector. For example, your server has two versions of your asset. One at 16px by 16px, the other at 32px by 32px. You browse to an associated page and your browser asks for the 16px by 16px version (by means of a header). The server sees two versions in storage and sends the correct one.

Apache already does this for languages, if you ask it to.

Re:We're in an icon-sharpness limbo by LachlanArthur on Sunday March 25, 2012 @09:27PM (#3754522)
Multi-resolution => maybe similar to .ico?