As of today we now seem do have discussed nearly every different angle of responsive images with its problems.
We recently figured out that
- We don’t want to provide a general responsive element.
We only want to provide a responsive image-element (no other media)
Read here why
- We already have a working polyfill for our proposed solution by Scott Jehl.
- There is a problem about bandwidth. We need to figure out how we can implement bandwidth queries into our picture-element. This needs to be solved now. Try to solve it!
- We saw several attempts of responsive image solutions. All are more a polyfill than a real solution. This is not what we want to have for production later.
- Yet another responsive image system
- Responsive Content Images using a spacer PNG and background-image
- The new elephant: Image Quality and Retina Displays
- We now have a CSS variant of responsive images with image-set(). This is great but not our goal. So please use this later for styling purposes but not for the real HTML-content. Read more
- We need a way to centralize media-queries. Read more
Then we have the second important point we recently figured out: A responsive file-format. This is what people think would be a great approach to work with responsive images. Unfortunately this is not easy and it is not our primary goal that we care about this. Nevertheless I would like to see some people pinging the right people (e.g. WebP-team) so they might be aware of the problem.
So we have all this solutions and thoughts written and discussed. When we have discussed and solved the outstanding issues, we need to start writing a specification for our picture-element I think.
If I have not missed a very important point here, let’s do this.
And don’t hesitate to maintain our Wiki please. This is the place where all our summarizing thoughts should be – not here in this blog-system.