Re: RFC: AtkText simplification
Trevor Saunders <[email protected]> Sun, 5 May 2013 21:37:33 -0400
| Newsgroups | gmane.comp.gnome.accessibility.devel |
|---|---|
| Message-ID | <20130506013733.GA4121@iceball> |
On Sun, May 05, 2013 at 09:18:49PM -0400, Joanmarie Diggs wrote: > On 05/05/2013 05:52 PM, Mario Sanchez Prada wrote: > > > So, let me get this straight... does this mean I do not have to > > implement the after/before variants AT ALL in WebKitGTK+ and that I only > > have to consider the START boundary? > > PiƱeiro should officially deprecate the after/before variants in ATK. > But from a functional point of view, Orca (the main if not the only > consumer of this stuff) is no longer using them. > > I've not yet looked at the start/end stuff. I'll try to do that this week. I wonder if there is a reason you prefer this approach to the ia2 one in which after / before varients are kept, but only the actual contents of the word / line / whatever are returned not the word / line and the whitespace before or after depending? thanks! Trev > > Thanks and take care. > --joanie > _______________________________________________ > gnome-accessibility-devel mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel