Skip to content
This repository was archived by the owner on Jan 16, 2026. It is now read-only.

Fixed breakpoint selection: it always opt-in for the biggest available breakpoint to fit the container size - #86

Merged
thom4parisot merged 8 commits into
masterfrom
fix-86
Mar 20, 2014
Merged

Fixed breakpoint selection: it always opt-in for the biggest available breakpoint to fit the container size#86
thom4parisot merged 8 commits into
masterfrom
fix-86

Conversation

@thom4parisot

Copy link
Copy Markdown
Contributor

Hi,

I had a container div with no width or max width set. My maximum image size in Imager was 976px. Imager works as normal when my browser resizes anywhere beneath 976px, but the moment my viewport (and therefore the container div) is wider than 976px, Imager defaults to the smallest image (320px).

So the effect goes from 976px - fine => 977px - blurry, when the expected behaviour is to keep the largest possible image.

Hope I've explained everything sufficiently!

@Integralist

Copy link
Copy Markdown
Contributor

@ChrisBAshton All explained perfectly. Thanks for raising this issue.

@thom4parisot

Copy link
Copy Markdown
Contributor

The tests fails but basically it has to be related with the max screen size of the iPhone (which is smaller that 1024 in portrait mode).

thom4parisot pushed a commit that referenced this pull request Mar 20, 2014
Containers above max image size load smallest image
@thom4parisot
thom4parisot merged commit 55d0071 into master Mar 20, 2014
@thom4parisot
thom4parisot deleted the fix-86 branch March 20, 2014 10:12
@thom4parisot thom4parisot changed the title Containers above max image size load smallest image Fixed breakpoint selection: it always opt-in for the biggest available breakpoint to fit the container size Mar 20, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants