This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28993 - pattern-tabpanel Changes
Summary: pattern-tabpanel Changes
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Practices (show other bugs)
Version: 1.1
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: James Nurthen
QA Contact:
URL: https://rawgit.com/w3c/aria/jn-tab-pa...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-27 18:30 UTC by James Nurthen
Modified: 2016-03-07 23:36 UTC (History)
1 user (show)

See Also:


Attachments

Description James Nurthen 2015-07-27 18:30:41 UTC
* Change order in description to

tabbed interface component
tab list
tab
tab panel

* Change tablist to 2 words in the above

* First 2 sentences become

A tabbed interface component is a set of layered areas, known as tab panels, where only one area is displayed at a time. The tabs are arranged along one of the edges of the contents but most commonly are found at the top. The user navigates and makes the contents of each area visible by interacting with the title "tab". Terms for understanding Tab Panels include:

* Keyboard Section

rewrite to allow selection to be made manually with space or enter rather than automatically

* Drop Control+Up, Control+PageUp, Control+PageDown.

* Michiel to look at possible replacements for Control_PageUp,Down etc.

Still debating Alt+Delete
Comment 1 James Nurthen 2016-02-29 19:32:37 UTC
Add keystroke for Delete when on the tab
Remove Alt_Delete as no one has done it.

Create a branch for tab including navigation on space/enter.
Comment 2 Michiel Bijl 2016-02-29 22:53:27 UTC
Thanks to my crappy connection today, I didn't follow the entire discussion:

> Michiel to look at possible replacements for Control_PageUp,Down etc.

Do I still need to look into this or will we drop that too? If we can recommend just shift tabbing back to the tab list. Although that could cause problems with tab panels with lots of focusable elements in them.
Comment 3 James Nurthen 2016-02-29 23:05:15 UTC
I think we are just going to drop it unless you have a desire to do the investigations.
Comment 4 Michiel Bijl 2016-02-29 23:07:14 UTC
Nah, I think we can just drop it, but I will keep it in mind. If I come up with a solution to the problem (or StommePoes batters me for supporting the removal of a keyboard feature), we can always add that.