Re: [whatwg] [html5] HTMLMapElement.images

[Ian Hickson]

On Sun, 2 Jul 2006, Shadow2531 wrote:
>
> On 7/1/06, dolphinling <[EMAIL PROTECTED]> wrote:
> > Can you even have an image map on an  ?
> 
> Yes

This is no longer allowed in the spec, actually. Is that a problem?

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Re: [whatwg] [html5] HTMLMapElement.images

[Ian Hickson]

On Sat, 1 Jul 2006, dolphinling wrote:
> Anne van Kesteren wrote:
> > Quoting Shadow2531 <[EMAIL PROTECTED]>:
> > > On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
> > > > Before I forget about this hereby a proposal to give the
> > > > HTMLMapElement interface a new (readonly) member called `images` or
> > > > equivalent representing an HTMLCollection consisting of
> > > > HTMLImageElement and HTMLObjectElement (and perhaps
> > > > HTMLCanvasElement?) elements that use that image map definition.
> > > 
> > > Do you want the INPUT element in the collection too? (because of
> > > type="image")
> > 
> > Probably only when type="image", but yes.
> 
> Can you even have an image map on an  ?

You can in HTML4, Firefox, and Opera (and now HTML5).

You can't in IE and Safari.

Should we drop it? My research indicates there's an insignificant number 
of pages with usemap="" attributes on  elements (on the 
order of 0.008%).

Anyway, I've added the attribute Anne suggested to the  element.

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Re: [whatwg] [html5] HTMLMapElement.images

[Shadow2531]

On 7/1/06, dolphinling <[EMAIL PROTECTED]> wrote:

Can you even have an image map on an  ?


Yes

--
burnout426

Re: [whatwg] [html5] HTMLMapElement.images

[dolphinling]

Anne van Kesteren wrote:

Quoting Shadow2531 <[EMAIL PROTECTED]>:

On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:

Before I forget about this hereby a proposal to give the
HTMLMapElement interface a new (readonly) member called `images` or
equivalent representing an HTMLCollection consisting of
HTMLImageElement and HTMLObjectElement (and perhaps
HTMLCanvasElement?) elements that use that image map definition.


Do you want the INPUT element in the collection too? (because of  
type="image")


Probably only when type="image", but yes.


Can you even have an image map on an  ?

--
dolphinling

Re: [whatwg] [html5] HTMLMapElement.images

[Lachlan Hunt]

Anne van Kesteren wrote:
Basically finding the position of the associated image elements so that 
you can show "popups" and so more easily without hardcoding that a 
particular image belongs to that map and vice versa.


  https://bugzilla.mozilla.org/attachment.cgi?id=67731&action=view

... has a nice example (works in Internet Explorer only).


Interesting.  The concept is a lot like these examples in recent A List 
Apart article:


http://alistapart.com/articles/cssmaps
* http://alistapart.com/d/cssmaps/stickymap/
* http://alistapart.com/d/cssmaps/multiple/

The difference with those, however, is that they're not marked up using 
, but rather the map is a background image with list items 
positioned over the top.


I've been thinking about this a little since that article was published 
and I think we need to work on improving the semantics and functionality 
of , so that it can handle things like that easily, without 
excessive CSS positioning and JavaScript.


Being able to semantically associate areas on a map with related content 
that can then be shown in a variety of ways, such as a tooltip on hover 
or click.  It would also be cool if it were easier to do something like 
the many similar features found in Google Maps.


--
Lachlan Hunt
http://lachy.id.au/

Re: [whatwg] [html5] HTMLMapElement.images

[Anne van Kesteren]

Quoting Shadow2531 <[EMAIL PROTECTED]>:

On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:

Before I forget about this hereby a proposal to give the
HTMLMapElement interface a new (readonly) member called `images` or
equivalent representing an HTMLCollection consisting of
HTMLImageElement and HTMLObjectElement (and perhaps
HTMLCanvasElement?) elements that use that image map definition.


Do you want the INPUT element in the collection too? (because of   
type="image")


Probably only when type="image", but yes.


--
Anne van Kesteren

Re: [whatwg] [html5] HTMLMapElement.images

[Anne van Kesteren]

Quoting Ian Hickson <[EMAIL PROTECTED]>:

On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:

Before I forget about this hereby a proposal to give the
HTMLMapElement interface a new (readonly) member called `images` or
equivalent representing an HTMLCollection consisting of
HTMLImageElement and HTMLObjectElement (and perhaps
HTMLCanvasElement?) elements that use that image map definition.


What's the use case?


Basically finding the position of the associated image elements so  
that you can show "popups" and so more easily without hardcoding that  
a particular image belongs to that map and vice versa.


  https://bugzilla.mozilla.org/attachment.cgi?id=67731&action=view

... has a nice example (works in Internet Explorer only).


--
Anne van Kesteren

Re: [whatwg] [html5] HTMLMapElement.images

[Ian Hickson]

On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:

Before I forget about this hereby a proposal to give the
HTMLMapElement interface a new (readonly) member called `images` or
equivalent representing an HTMLCollection consisting of
HTMLImageElement and HTMLObjectElement (and perhaps
HTMLCanvasElement?) elements that use that image map definition.


What's the use case?

--
Ian Hickson

Re: [whatwg] [html5] HTMLMapElement.images

[Shadow2531]

On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:

Before I forget about this hereby a proposal to give the
HTMLMapElement interface a new (readonly) member called `images` or
equivalent representing an HTMLCollection consisting of
HTMLImageElement and HTMLObjectElement (and perhaps
HTMLCanvasElement?) elements that use that image map definition.


Do you want the INPUT element in the collection too? (because of type="image")

--
burnout426

[whatwg] [html5] HTMLMapElement.images

[Anne van Kesteren]

Before I forget about this hereby a proposal to give the  
HTMLMapElement interface a new (readonly) member called `images` or  
equivalent representing an HTMLCollection consisting of  
HTMLImageElement and HTMLObjectElement (and perhaps  
HTMLCanvasElement?) elements that use that image map definition.



--
Anne van Kesteren