[
https://issues.apache.org/jira/browse/TRINIDAD-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732472#action_12732472
]
Carsten Pieper commented on TRINIDAD-888:
-----------------------------------------
Specific use cases? Hm, I'm not quite sure, what you mean...
If this might have been the question: We (developers) love using the
tr:panelFormLayout. If you tab through its content, the order is "columns
first". In almost all cases, our customers would prefer a "row first" tabbing
strategy...
Or have you been asking about the preferred tabIndex strategy? Well, wouldn't
it make sense to follow the W3C approach
(http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex)?
> Add support for tabindex to focusable components
> ------------------------------------------------
>
> Key: TRINIDAD-888
> URL: https://issues.apache.org/jira/browse/TRINIDAD-888
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Components
> Affects Versions: 1.0.5-core, 1.2.5-core
> Reporter: Andrew Robinson
> Assignee: Andrew Robinson
> Priority: Minor
>
> Add support for tabindex to focusable components (initial list, maybe changed
> during implementation):
> breadCrumbs
> chooseColor
> chooseDate
> commandButton
> commandLink
> commandNavigationItem
> goButton
> goLink
> inputColor
> inputDate
> inputFile
> inputListOfValues
> inputNumberSpinbox
> inputText
> navigationPane
> navigationTree
> panelAccordion
> panelPopup (not with hover?)
> panelRadio/showDetailItem
> panelTabbed
> processChoiceBar
> resetButton
> selectBooleanCheckbox
> selectBooleanRadio
> selectManyCheckbox
> selectManyListbox
> selectManyShuttle
> selectRangeChoiceBar
> showDetail
> singleStepButtonBar
> table
> train
> tree
> treeTable
> According to the w3c:
> http://www.w3.org/TR/html4/interact/forms.html#adef-tabindex
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
