Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breakpoint change/feature -request #77

Closed
dinbror opened this issue Mar 1, 2016 · 2 comments
Closed

Breakpoint change/feature -request #77

dinbror opened this issue Mar 1, 2016 · 2 comments

Comments

@dinbror
Copy link
Owner

dinbror commented Mar 1, 2016

To avoid redundancy I'm bundling all the issues and pull requests that is about the wish to change how the breakpoints works today:

Issues:
#74
#67
#57
#42

Pull requests (thanks @andr3pt):
#50
#40

How the breakpoints works today:

The breakpoints are defined by the device width not the browser width. It means that it’ll look at your screen width which won’t change when you resize your browser window.
The reason why I’m looking at the device width and not the width is that I don’t want to load multiple image sources for the same image when you resize (multiple server request per image). And if you have a big screen but the initial width of your browser window is something small I don’t want to upscale a low res image when you resize it up.

The future

I'll look into a bigger refactoring of the code where I of course will take all your wishes into consideration. I see your point and I am not sure I can continue with not implementing it 😄

Keep up all your good suggestions and any help is appreciated.

@dinbror
Copy link
Owner Author

dinbror commented Apr 30, 2016

The "Breakpoints" feature is marked as obsolete in version 1.6.0. Use srcset and/or the picture element instead

@dinbror dinbror closed this as completed Apr 30, 2016
@iamrobert
Copy link

picture element responsive example:
http://dinbror.dk/blazy/examples/?ref=blog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants