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.
Let me make sure I understand what you're saying here. Is it that
WebKit does not want to properly render properly authored HTML4
content, but only HTML5 content? If this is the case I think that
should be clearly stated on the goals of the project page. If that's
not the case, then I see no problem with WebKit supporting an HTML4
construct even if it is eventually removed in ten years by HTML5.
Take care,
Rob
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
