Single line means that it is a single line *text field*. Will there be a problem in office applications where editable text is applied? ... is it really a single or multi-line as it is a document? In other words, is there an issue if we assume single line? In documents it may mean neither single or multi-line.
If we delete it we will also have a conflict with ATK and Java which have single and multi-line: http://library.gnome.org/devel/atk/unstable/atk-AtkState.html#AtkStateType http://java.sun.com/j2se/1.5.0/docs/api/javax/accessibility/AccessibleState.html It is been a long time but the purpose for single line and multiple line was to help ATs with Braille devices to know whether to break up the text, by line , for a text field. Obviously, a text field that is single line is rather easy to deal with. When You use mult-line you know to break up each line of text by rows. This really that trivial for documents. Rich Schwerdtfeger CTO Accessibility Software Group Carolyn MacLeod <Carolyn_MacLeod@ ca.ibm.com> To Sent by: David Bolter accessibility-ia2 <[email protected]> [email protected] cc nuxfoundation.org [email protected] tion.org Subject 04/09/2010 04:42 Re: [Accessibility-ia2] Deprecation PM of IA2_STATE_SINGLE_LINE Isn't role pretty much always the first thing an AT asks any accessible object? Carolyn Re: [Accessibility-ia2] Deprecation of IA2_STATE_SINGLE_LINE David Bolter to: accessibility-ia2 04/09/2010 03:11 PM Sent by: [email protected] on.org The only concern I have is that Firefox has exposed it for a while; although that doesn't necessarily stop deprecation. Also I think Alexander's point is valid here: http://www.mail-archive.com/[email protected]/msg00185.html Is it perhaps easier for AT to just check the state bit, rather than the role as well? cheers, David On 09/04/10 2:33 PM, Carolyn MacLeod wrote: Going once, going twice.... ? I need to decide whether or not to delete the single-line state bit from the Eclipse API before April 30. Carolyn From: Pete Brunet <[email protected]> To: IA2 List <[email protected]> Date: 26/03/2010 09:21 AM Subject: [Accessibility-ia2] Deprecation of IA2_STATE_SINGLE_LINE Sent by: [email protected] The following is (slightly edited) from Carolyn, who is implementing IA2 in Eclipse... Back in the fall, Andres asked why IA2 provides both IA2_STATE_MULTI_LINE and IA2_STATE_SINGLE_LINE state bits. http://www.mail-archive.com/[email protected]/msg00173.html They would seem to be mutually exclusive, and having both takes up a precious bit in the 32-bit strip. Is there ever a case where an object can be neither single-line nor multi-line? Is there ever a case where an object can be both single-line and multi-line? In the conversation on the ia2 list, Jamie said that he had never even noticed the single-line bit. This is a possible source of error, for example if an application only notices and sets/clears the "single" bit, but the AT only looks at the "multi" bit. The list discussion kind of ended with "oh well, whatever". I propose deprecating IA2_STATE_SINGLE_LINE. Any objections? _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
<<inline: pic23672.gif>>
<<inline: ecblank.gif>>
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
