Add tabIndex attribute to appropriate components
------------------------------------------------
Key: TRINIDAD-100
URL: https://issues.apache.org/jira/browse/TRINIDAD-100
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Components
Affects Versions: 1.0.2-core
Reporter: Danny Robinson
No Trinidad components have a tabindex attribute, which makes it impossible to
control tab-order. While tabindex isn't a fantastic solution to tab ordering,
it is well known and a standard part of HTML. Until we have a better solution,
we should add a tabIndex attribute.
Some context from previous emails
Danny:
I noted Eric created issue ADFFACES-482 to have tabindex added to all
components. I know this has come up before and general comments were around
its limitations, however even with its limitations (ie. no dynamic calculation
for subviews etc.) I still feel it would be better to have this attribute than
the complete lack of support for any navigation ordering that Trinidad has
currently.
Adam:
I'm +0... never liked the HTML attribute much, but there's
demand for it... Two design questions before going forward:
- Should it be tabindex or tabIndex?
Trinidad generally uses camel-case. I prefer tabIndex.
- Should the attribute be on components that ordinarily do not
have navigation?
Danny says "all components". You could, in theory, put tabindex
on a ordinary span in HTML, so we could add it to outputText,
etc... However, I'd rather not - it's extra overhead for a rarely
used feature, and unused attributes *are* a performance problem,
especially for outputText and panel components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
