- From: David Newton <david@davidnewton.ca>
- Date: Sun, 3 Nov 2013 15:13:08 -0500
- To: Anselm Hannemann <info@anselm-hannemann.com>
- Cc: Yoav Weiss <yoav@yoav.ws>, Attiks <attiks@gmail.com>, Mathew Marquis <mat@matmarquis.com>, François REMY <francois.remy.dev@outlook.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "Podjarny, Guy" <gpodjarn@akamai.com>, Aaron Gustafson <aaron@easy-designs.net>, Marcos Caceres <marcos@marcosc.com>, Robin Berjon <robin@w3.org>, Shane Hudson <shane@shanehudson.net>, "public-respimg@w3.org" <public-respimg@w3.org>
On Nov 3, 2013, at 3:03 PM, Anselm Hannemann <info@anselm-hannemann.com> wrote: >> What about just letting usemap take a list of IDs in the same order as src-n? >> >> <img usemap=“#map1, #map” src-1=“(max-width: 400px) img1.png” src-2=“(max-width: 1000px) img2.png” alt=“whatever” /> > > This is not possible for the very same reason we couldn’t extend the src-attribute. We would need to create a new attribute usemap-n="". > I find this an ugly solution. Still, not supporting usemaps attribute when a src-n attribute exists is also ugly. What are those reasons specifically? Not saying you’re wrong, but just wondering if the less frequent usage of usemap could make the problems easier to tackle than they were with src. That said, even though usemap-N isn’t ideal, the infrequency with which it would be needed makes it not a terrible compromise IMO. > Can someone find out if it would be possible to drop this attribute at all? There are enough better solutions like working with SVG for such maps. > I also think we should ensure every img attribute is somehow supported by src-N. Otherwise it’s not a good webstandard-solution. Partial support doesn’t sound bullet-proof which a webstandard spec should be IMO. Other attributes to consider: ismap, crossorigin. Crossorigin should be fine; ismap poses similar problems to usemap.
Received on Sunday, 3 November 2013 20:13:46 UTC