high density support is hard coded

[FossPrime]

Currently the CSS pixel ratio support requires a lot of manual labor, is not scalable and does not support 3x displays such as the HTC One, HTC DNA, Galaxy S4, Oppo Find 5 and the LG Optimus G Pro.

Instead of explicitly declaring a src-retina attribute, why not allow us to declare the file naming convention of high density images. By default it would be '-retina' or '-2x' but we could support '-%N%' to
indicate a natural device pixel ratio and '-%Z%' to support fractional pixel ratios using a fancy back end.

That would be scaleable, but not entirely practical for many applications due to bandwidth constraints. The best alternative would be to send headers/cookies to the server and let it determine what experience we will receive based on the connection type and density. This would require a lot of back end support. But the end result is quite elegant, as the server could choose to serve 2x images to all 3x devices that are not on WiFi or LTE. The default connection would be 'unknown'.

Then again, support for both is not a tall order. Though at that point, it starts to become its own script.

[luis-almeida]

@Reyncor No doubt that allowing different resolutions would be a nice improvement.

I believe a similar request has already been made in #16

[LasseRafn]

I just don't think this feature fits this plugin, it's meant to be lightweight and only with the particular functionality, not a lot of functions that people don't use.

[FossPrime]

Times have changed, source set and browser hints seems to be the way
forward, with a lot of back end support. To this day, I don't know of a
solid solution that will work on a Lamp.
On Sep 30, 2014 9:23 AM, "Lasse Rafn" notifications@github.com wrote:

I just don't think this feature fits this plugin, it's meant to be
lightweight and only with the particular functionality, not a lot of
functions that people don't use.

—
Reply to this email directly or view it on GitHub
#9 (comment).