3 ms·
We actually talked to some Safari engineers about this and the response was that image-sets were the way forward. I am not sure I agree. The key argument was th
by zacman85 14y ago
We actually talked to some Safari engineers about this and the response was that image-sets were the way forward. I am not sure I agree. The key argument was that the accepts header puts the burden entirely on the server and does not account for multi-resolution environments, such as multiple monitor setups. Content moving from one device/monitor to another could make use of image-sets to load in the appropriate image for its display.
- WiseWeasel 14y agoI wish image-set was more efficient to use. I'm way too lazy to maintain explicit lists of every variant file path for every image if I can avoid it (which should be possible if we take advantage of systematic file naming conventions already commonly in place). I'd take this proposed solution over image-set, simply because it avoids that extra work, not to mention being more backwards-compatible; image-set would require you to list the path for the 1x asset of an img element in both the 'src' attribute and the image-set attribute in order to maintain backwards-compatibility.