It can be frustrating seeing this Community Group go quiet, especially following a surge in traffic that very literally brought the Community Group site down. We have to understand\u2014and I\u2019m speaking in no small part to myself, here\u2014that most standards folks have a massive backlog of issues and suggestions to work through. With that in mind: even as public-facing as this Community Group is, it\u2019s a lot to ask of members of the standards bodies or browser teams to parse though several pages of prose and leaf through comments for the meat of this thing.<\/p>\n
For that reason I\u2019ll be making a first pass at a draft spec myself. Not with any intent to see it codified word for word, mind you, but to break down the core details of this new responsive images element in the most efficient and easily parsed way. All signal, no noise. This will be a big departure for me, since\u2014as many of you know\u2014I\u2019m especially noise inclined.<\/p>\n
We\u2019ve done a lot of work reasoning this thing out and adapting it to community feedback to get it to this point: a point where it feels like it may be ready for sample implementation. I find this particularly exciting\u2014like many of you, I fell into this website-making gig because it afforded me a chance to solve new and exciting problems. There\u2019s not much I enjoy more than seeing a solution to a tricky issue come to life, and I\u2019m certain that\u2019s a sentiment shared by many browser developers.<\/p>\n
If you\u2019re a similarly-inclined browser developer, I\u2019d love to work with you on a sample implementation of the If this is something you think that you or your team might be interested in exploring, I\u2019d love to hear from you while the draft spec is coming together.<\/p>\n","protected":false},"excerpt":{"rendered":" It can be frustrating seeing this Community Group go quiet, especially following a surge in traffic that very literally brought the Community Group site down. We have to understand\u2014and I\u2019m speaking in no small part to myself, here\u2014that most standards … Continue reading <picture><\/code> element. I wouldn\u2019t expect anyone to barrel ahead with this based on the content of this group or an email exchange with me, but rather once we have a pared-down and easily-distributed example spec to reference along the way. Of course, it goes without saying that I\u2019m more than happy to work alongside vendors in whatever capacity I can.<\/p>\n