Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-12 Thread Aryeh Gregor
On Wed, Jan 11, 2012 at 3:09 PM, Charles Pritchard ch...@jumis.com wrote: The reason is listed in WCAG2 section 2.1.2 and CR5. http://www.w3.org/TR/WCAG/ The items suggest that a standard means of moving focus be maintained. Users should be given simple instructions on how to move focus if

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-12 Thread Tab Atkins Jr.
On Thu, Jan 12, 2012 at 8:41 AM, Aryeh Gregor a...@aryeh.name wrote: On Wed, Jan 11, 2012 at 3:09 PM, Charles Pritchard ch...@jumis.com wrote: The reason is listed in WCAG2 section 2.1.2 and CR5. http://www.w3.org/TR/WCAG/ The items suggest that a standard means of moving focus be maintained.

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-11 Thread Aryeh Gregor
On Tue, Jan 10, 2012 at 4:48 PM, Charles Pritchard ch...@jumis.com wrote: Would users press Esc to get out of the tab lock? Do they need to be able to get out of it? They can't in a regular word processor, so why should they be able to in Google Docs? If some users need to be able to override

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-11 Thread Charles Pritchard
On 1/11/2012 8:15 AM, Aryeh Gregor wrote: On Tue, Jan 10, 2012 at 4:48 PM, Charles Pritchardch...@jumis.com wrote: Would users press Esc to get out of the tab lock? Do they need to be able to get out of it? They can't in a regular word processor, so why should they be able to in Google Docs?

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-11 Thread Ojan Vafai
On Wed, Jan 11, 2012 at 8:15 AM, Aryeh Gregor a...@aryeh.name wrote: On Tue, Jan 10, 2012 at 4:48 PM, Charles Pritchard ch...@jumis.com wrote: Historically, one of my biggest frustrations with contentEditable is that you have to take it all or none. The lack of configurability is

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-10 Thread Aryeh Gregor
On Fri, Jan 6, 2012 at 10:12 PM, Ojan Vafai o...@chromium.org wrote: There are strong use-cases for both. In an app like Google Docs you certainly want tab to act like indent. In a mail app, it's more of a toss-up. In something like the Google+ sharing widget, you certainly want it to maintain

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-10 Thread Charles Pritchard
On Jan 10, 2012, at 12:30 PM, Aryeh Gregor a...@aryeh.name wrote: On Fri, Jan 6, 2012 at 10:12 PM, Ojan Vafai o...@chromium.org wrote: There are strong use-cases for both. In an app like Google Docs you certainly want tab to act like indent. In a mail app, it's more of a toss-up. In something

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-10 Thread Ojan Vafai
On Tue, Jan 10, 2012 at 12:30 PM, Aryeh Gregor a...@aryeh.name wrote: On Fri, Jan 6, 2012 at 10:12 PM, Ojan Vafai o...@chromium.org wrote: We should make this configurable via execCommand: document.execCommand(TabBehavior, false, bitmask); I'm leery of global flags like that, because they

Re: [editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-07 Thread timeless
Ojan Vafai o...@chromium.org wrote: We should make this configurable via execCommand: document.execCommand(TabBehavior, false, bitmask); The bitmask is because you might want a different set of behaviors: -Tabbing in lists -Tabbing in table cells -Tabbing blockquotes -Tab in none of the

[editing] tab in an editable area WAS: [whatwg] behavior when typing in contentEditable elements

2012-01-06 Thread Ojan Vafai
BCC: whatwg, CC:public-webapps since discussion of the editing spec has moved On Tue, Jun 14, 2011 at 12:54 PM, Aryeh Gregor simetrical+...@gmail.comwrote: You suggest that the tab key in browsers should act like indent, as in dedicated text editors. This isn't tenable -- it means that if