[webkit-dev] image maps to be focused via tab

Maciej Stachowiak mjs at apple.com
Fri Nov 14 15:19:21 PST 2008

On Nov 14, 2008, at 3:14 PM, Rob Burns wrote:

> Hi Maciej,
> On Nov 14, 2008, at 5:07 PM, Maciej Stachowiak wrote:
>> On Nov 14, 2008, at 2:48 PM, Rob Burns wrote:
>>> On Nov 14, 2008, at 4:01 PM, Maciej Stachowiak wrote:
>>>> One particularly wrong aspect of the original assumption is that  
>>>> in practice, a single <map> and all its <area>s can be used by  
>>>> multiple <img> elements. So representing focus of individual  
>>>> image map active areas by making the <area> node focused won't  
>>>> really work - it doesn't fit into the single focus ring model,  
>>>> since just focus on the <area> node doesn't tell you which image  
>>>> map is active.
>>> Let me add that image maps also apply to input elements of type  
>>> image and object elements when they embed a still image (content- 
>>> type image/*).
>> This is a completely unrelated issue, and your claim of what image  
>> maps apply to is inconsistent with the current HTML5 draft. I know  
>> you have a longstanding disagreement with this aspect of the HTML5  
>> spec, but this is probably not a point where the WebKit project  
>> would want to diverge from the spec.
> I just want to remind you that the HTML5 spec is only a draft. The  
> editor predicts a final version in over a decade. So I don't think  
> we need to treat it as authoritative. Also in the future when citing  
> violations of a spec, it would be best to provide a specific  
> reference so other's can follow your reading of that spec. As for  
> this issue of AREA element's I'm not sure how you're reading what I  
> proposed as a violation of any spec.

In HTML5, image maps do not apply to input elements of type image. You  
have in the past filed bug reports against WebKit requesting support  
for this, or smuggled it into other requests, without citing the  
current state of the spec. I think that is disingenuous. WebKit  
developers deserve fair warning so they don't accidentally rely on  
your representations instead of the spec.


More information about the webkit-dev mailing list