On 6/08/2010 12:31 AM, Pete Brunet wrote: > It has been requested that a means be provided to get the current line > number of a text control (i.e. the line number that the caret is > currently on). It might be useful to do this for individual pieces of text, rather than just the caret; see below.
> Apparently Firefox returns a "line-number" field in the object > attributes for a text control. > What are your thoughts on adding line-number to the [IA2 object attributes] > spec? The problem with using an object attribute is that it restricts this feature to the caret. It might also be useful to be able to query the line number for any given piece of text. To allow this, it needs to be a text attribute. Getting the line number for the caret would then simply involve fetching the text attributes for the caret offset. > By the way, the IA2 object attribute spec was started when Symphony was > done but FF IA2 support was still not complete. So a larger question is > if we should harmonize the current IA2 and FF object attribute specs, > hopefully borrowing from other mature specs like CSS2 (or maybe even > CSS3). I think this is perhaps a good idea. > Or should we eliminate the IA2 object attribute spec and instead > have each app document its own object attributes. I think this is a bad idea. :) It will lead to too many different implementations which require special cases. This rather defeats the point of IA2 being a standard. It's bad enough that we already have two ways of representing a document; i.e. Symphony's "object per paragraph" approach and Gecko's "hierarchy of embedded objects" approach. ATs need to move away from special casing for every different application and this would not help in that move. Jamie -- James Teh Vice President NV Access Inc, ABN 61773362390 Email: [email protected] Web site: http://www.nvaccess.org/ _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
