I am not sure about this but I do think we cannot postpone this for an img attribute solution. As usemap is an attribute referring to the img element’s source (in this case src-N) it should (must??) be supported by src-N. For picture, as this is a completely new and different element, there is no need to support it though. Best regards, Anselm Hannemann On 03.11.2013, at 10:22, Yoav Weiss <yoav@yoav.ws> wrote: > Good question! > > For picture we decided at the time to postpone usemap support to a later phase. Unless people consider this critical, I think we can do the same for srcN. (baby steps and all that) > > > > On Sun, Nov 3, 2013 at 10:08 AM, Attiks <attiks@gmail.com> wrote: > Hi, > > How will srcN handle the use of the usemap attribute? Will it introduce a srcmapN attribute or not support it at all? > > > On Mon, Oct 7, 2013 at 5:05 PM, Marcos Caceres <marcos@marcosc.com> wrote: > > > > On Monday, October 7, 2013 at 3:56 PM, Yoav Weiss wrote: > > > I believe a dataset()-like API would be pretty natural to add, if the need arises later on. > > > > Exactly. Just remembering that Rick Waldron did a bit of experimenting with a "srcset API" back in the day (mostly to show how crappy srcset is to work with ATM). We could always resurrect that and get Rick to help us out. > > -- > Marcos Caceres > > > > > >Received on Sunday, 3 November 2013 15:07:52 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:10 UTC