RE: Suddenly confused about today's repeat index discussion

Yes but if you click the group, does it change the repeat index?

Also does FF then go into every inner repeat (and every one of their inner 
repeats and so on) to change their indexes?

FYI, in our implementation, setting focus to a container like a group or a 
repeat or a switch is handled specially because those objects cannot 
directly take the focus.  They can only own it indirectly by owning the 
control that has the focus.  So, we seek out the first item within the 
container that can accept the focus and send it there (which may involve 
drilling into inner repeats, switch cases, or groups to find).  So, the 
end-user control gets the DOMFocusIn, which bubbles up to the container.

Cheers,
John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer





"Kugelman, John" <jkugelman@progeny.net> 
Sent by: public-forms-request@w3.org
08/13/2007 07:21 AM

To
<ebruchez@orbeon.com>, "Forms WG (new)" <public-forms@w3.org>
cc

Subject
RE: Suddenly confused about today's repeat index discussion







FormFaces behaves the same way.

--
John Kugelman, FormFaces

-----Original Message-----
From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of Erik Bruchez
Sent: Sunday, August 12, 2007 3:51 AM
To: Forms WG (new)
Subject: Re: Suddenly confused about today's repeat index discussion

<snip>

I don't think our implementation dispatches DomFocusIn on groups:
i.e., if you focus on a control within a group, you will get
DOMFocusIn, and that will bubble, but if you click on the area of the
group outside any other control, then we don't dispatch the
event. What do other implementations do?