Andrew Robinson wrote:
entering the color with keyboard is a good point, so I agree not a
showstopper,
For the spinbox I agree it's a much less annoying case than the
chooseColor, but still, I agree with Matthias that 1 tab stop would be
preferable to 3.
Actually, with chooseColor there are usually 49 tab stops (cells with
links in them):
http://www.irian.at/trinidad-demo/faces/components/chooseColor.jspx
(the chooseColor is the palette, not the input element)
sure, Matthias brought up the number of tab stops for the
inputNumberSpinbox as a related tab stop issue, and I was commenting on
that.
So what do you feel for this bug, no tabindex on chooseColor, or use 1
in the first cell and file a bug for keyboard support and to ensure
focus is able to be determined? (tabbing 49 times is REALLY bad)
Hmm, well I guess there's not much point to tabbing there if you can't
move around, so I say no stop and a bug for keyboard support....
I'm confused though, are you just controlling the number of tab stops in
the implementation? Meaning you're not trying to add a public api for
the user to control tab stops on the page, are you?
Gab
