[
https://issues.apache.org/jira/browse/TRINIDAD-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733706#action_12733706
]
Blake Sullivan commented on TRINIDAD-888:
-----------------------------------------
Marco, I'm having a hard time picturing you panelFormLayout issue. The base
issue here is what the abstraction or abstractions for controlling tabbing
should be--both programmatic and declarative. To do that we need use cases
like yours to ensure that we're covering the correct ground. I'm pretty
certain that even if we were willing to make multiple passes through the
component tree, rendering tabIndex would not be sufficient and that we will
have to manage focus explicitly using javascript.
> 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.
