- From: Simon Pieters <simonp@opera.com>
- Date: Thu, 26 Mar 2015 11:10:42 +0100
- To: whatwg@whatwg.org, "Martin Janecke" <whatwg.org@prlbr.com>
On Thu, 26 Mar 2015 01:47:57 +0100, Martin Janecke <whatwg.org@prlbr.com> wrote: > Am .03.2015, 16:08 Uhr, schrieb Simon Pieters <simonp@opera.com>: > >> […] >> >> It seems to me that there are two use cases: >> >> 1. variable-size image map >> 2. art direction image map >> >> (1) is more common than (2). > > Yes, you're right. > > >> If there is implementor interest, I think it makes sense to make <map> >> address use case (1) first, and after that maybe also use case (2). Is >> there? :-) > > I'd say there's a good chance that a solution for (1) could also cover > (2). So it might be helpful to keep (2) in mind while working on (1) in > order not to miss that chance … If there is implementor interest. How? Consider the "AMC Networks" image map in the footer of http://www.wetv.com/ . Make the window narrower than 600px, the image map will have a different layout. -- Simon Pieters Opera Software
Received on Thursday, 26 March 2015 10:11:10 UTC