[Bug 18384] Consider adding an adaptive image element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18384

--- Comment #7 from Mat Marquis <mat@matmarquis.com> 2012-07-25 13:41:40 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > On the other hand the specification could clearly state that all different
> > source elements needs to share the same subject matter. But if people start
> > (ab)using it the way I described above then there is no way for a validator to
> > check this.
> 
> Hi Peter,
> 
> I too worry that nothing is stopping authors from using different images and
> suggested possibility using responsive alt on source (see comment #1).
> 
> Alternatively we would need some very strong spec text to outlaw different
> images. Suggestions? Maybe in the future it could be made machine testable?
> There are such things as TinEye.
> https://addons.mozilla.org/en-US/firefox/user/3304309/?src=api

I think it’s going to be important that this be posed as a means of providing
alternate sources for *content* images (
http://www.bostonglobe.com/magazine/2012/07/22 or http://www.apple.com, for
example ). A banner that displays different decorative banners would be most
appropriately done in CSS -- this would likely be simpler for the authors as
well, especially given the new `img-set` CSS syntax. I’m sure we’re apt to see
`picture` used incorrectly for decorate images but no more than we already see
with `img`, I wouldn’t think.

It doesn’t hurt our case that this is such a high-profile issue in the dev
community, and that `picture` is likely to see use from advanced and highly
visible developers right away -- I think we’re likely to see a number of great
examples of `picture` usage springing up almost immediately, paving the way for
responsible usage in the future.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 25 July 2012 13:41:42 UTC