On Nov 14, 2008, at 9:15 AM, Darin Adler wrote:

On Nov 14, 2008, at 12:24 AM, browserwk wrote:

Before list, i assume html page have only one <img> and <map>(also one
<area>) tag, but also they are bounded.

In order to focus navigate via tab, i did follow things.
1 to identify <img>,<area> tag
I can get the <img> or <area> node from
Document::nextFocusableNode
Document::previousFocusableNode.

2 get absolutely position
Also, i had got the position of the <img> and each <area> node with
nonstandard way, in any way.
If i use areaNode->renderer(), i will got NULL.
I didn't know the reason.If u can, tell me more.

3 to focus <area> node
In this step, i fail to focus the <area> node, moreover didn't see the
focus ring.
And i found the <area> node never pass through the isKeyboardFocusable()
function.
So, some questions
<1> I want to know the factor that a node need be focusable, just like
<area> node.
<2> Can i render the focus ring, when i got the <area> node and it's
absolutely postion ?

This doesn't sound like the right approach. To make this work the approach would not to be write new code to navigate, but rather to change the existing code so that it will do this when necessary.

Assuming the page has only one <img>, one <map>, and one <area> seems completely wrong, and I'm not sure it's helpful to designing a solution.

The premises behind your questions <1> and <2> are wrong so I really don't see how I can answer the questions.

Sorry, I'd love to help, but I'm stuck here.

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.

Regards,
Maciej

_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Reply via email to