[Seaside] Question about WASelectTag class hierarchy...

Michel Bany m.bany at wanadoo.fr
Sat Apr 28 09:13:57 UTC 2007

Rick Flower a écrit :
> Hi all...
> I was trying to fix a form (using the Canvas API) that wasn't 
> specifying the #tabindex: to direct the browser how to deal with tab 
> key presses & form fields.  Anyway, I found that WASelectTag doesn't 
> seem to know anything about #tabindex.. In looking further into the 
> guts of how the classes were put together, I see that the #tabindex: 
> belongs to WAFormInputTag, but that WASelectTag isn't related to that 
> class (the hierarchy splits after WATagBrush).. Since WASelectTag is 
> part of a form, shouldn't it be related to WAFormInputTag?
I believe that you spotted something that will need to be fixed.
We have two different spelling for the same method
- #tabindex: in WAFormInput, and
- #tabIndex: in WATagBrush
So we have to make two decisions
- which one should be removed
- what spelling

I vote for WATagBrush>tabIndex: since we have WATagBrush>onChange:

More information about the seaside mailing list