Development:Planning:Focus Chain - Revision history

Sardisson: new bug

2007-08-31T05:06:34Z

new bug

2007-06-09T21:00:11Z

add pop-up blocker bug, and metabug

2007-06-09T20:46:08Z

go go gadget bugs

2006-10-17T03:47:02Z

note about blocker

2006-06-24T08:30:11Z

With FKA enabled: mismatched '

2006-06-24T08:24:09Z

With FKA enabled: switch to what Håkan actually implemented

2006-06-24T08:17:41Z

With FKA disabled: swap for what Håkan implemented

2006-06-24T08:02:22Z

2006-05-18T23:51:44Z

Assorted thoughts: update

2006-05-18T23:09:09Z

Issues with content-area tabbing: note about the Gecko pref

← Older revision		Revision as of 05:06, 31 August 2007
Line 1:		Line 1:
−	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}}, {{bug\|280963}}, {{bug\|346803}}, ~~and~~ {{bug\|383867}}'' (metabug {{bug\|383871}}	+	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}}, {{bug\|280963}}, {{bug\|346803}}, {{bug\|383867}}, {{bug\|392740}}'' (metabug {{bug\|383871}}

	All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.		All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.

← Older revision		Revision as of 21:00, 9 June 2007
Line 1:		Line 1:
−	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}}, {{bug\|280963}}, and {{bug\|383867}}''	+	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}}, {{bug\|280963}}, {{bug\|346803}}, and {{bug\|383867}}'' (metabug {{bug\|383871}}

	All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.		All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.

← Older revision		Revision as of 20:46, 9 June 2007
Line 1:		Line 1:
−	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}} and {{bug\|~~280963~~}}''	+	''Draft of a Focus Chain to fix {{bug\|152987}}, {{bug\|198153}}, {{bug\|336949}}, {{bug\|280963}}, and {{bug\|383867}}''

	All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.		All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.

← Older revision		Revision as of 03:47, 17 October 2006
Line 2:		Line 2:

	All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.		All of these assume a start-point of the location bar, though in most real-world cases we focus the content area (or some part of the Manager) after loading the page/Manager. The chain should pick up from whatever element is focused in those cases, so that auto-focused chains and chains where the user puts focus somewhere behave the same, no matter the starting point.
		+
		+	'''This needs to be updated to take the pop-up blocker into account'''

	==Web pages==		==Web pages==

@@ Line 33: / Line 33: @@
 * Tab bar first tab (''if Bookmark Bar is visible'')
 ** Tab proceeds through the active tabs and down-arrow moves the focus into the content area
-*:'''or, since the OS tab behavior is different''
+*:'''or, since the OS tab behavior is different'''
 ** Arrows go left/right along the tab bar (activating each tab as you reach it) and tab takes you into the content area
 **: I think we should do this; it's "cleaner" and how the OS works (and Firefox, but not Safari)

@@ Line 82: / Line 82: @@
 * ''into the Manager''
 ** Manager search field ('''actual initial focus''')
 ** Manager right (outliner) pane
 ** New Collection menubutton
 ** New separator/folder/etc. menubutton
@@ Line 94: / Line 94: @@
 ====Issues====
-* How do you access the menu in the search field (to select the filter type)?
+* How do you access the menu in the search field (to select the filter type)? - {{bug|339322}}
 * How do you access the column headings to change sort order or which field to sort upon?
 ** Or to resize them
-*: Some things just aren't (can't be) accessible here, just like you can't customize a Cocoa toolbar with a keyboard....
+*: Some things just aren't (can't be) keyboard-accessible here, just like you can't customize a Cocoa toolbar with a keyboard....
 ====Assorted thoughts====

← Older revision	Revision as of 08:02, 24 June 2006
(No difference)

← Older revision		Revision as of 23:51, 18 May 2006
Line 118:		Line 118:
	** ardissone: search -> outliner -> collections		** ardissone: search -> outliner -> collections
	** ardissone: maybe that's the determining factor, if we accept default focus is the mgr search field		** ardissone: maybe that's the determining factor, if we accept default focus is the mgr search field
		+
		+	* Except in this case we ended up doing what Apple recommends, upper right to bottom left, so focus moves from the search field (initial) to the Collections to the outliner (with FKA off); see {{bug\|337144}}.

@@ Line 23: / Line 23: @@
 * ideally, even when a page has focusable elements, we should initially set focus to the entire page, not the first form element, so that arrow key scroll, etc., work
 *: doing that might help with the above
 ===With FKA enabled===