After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 489828 - Provide ability to get character attributes at "insertion point"
Provide ability to get character attributes at "insertion point"
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: api
unspecified
Other All
: High enhancement
: ---
Assigned To: Li Yuan
Li Yuan
: 487918 (view as bug list)
Depends on:
Blocks: 477895
 
 
Reported: 2007-10-24 15:02 UTC by Willie Walker
Modified: 2009-06-03 09:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ATK patch (782 bytes, patch)
2009-05-21 08:12 UTC, Li Yuan
committed Details | Review
at-spi patch (976 bytes, patch)
2009-05-21 08:12 UTC, Li Yuan
committed Details | Review

Description Willie Walker 2007-10-24 15:02:01 UTC
Right now, the AT-SPI provides a getAttributeRun method in Accessibility_Text to allow an assistive technology to query the text attributes of existing text.  There are times, however, that the user wants to know what the attributes will be for the characters that will be inserted when they start typing.

For example, assume the user is typing in OOo and is using a default style where bold is turned off.  The user then back arrows two characters and presses Ctrl+b.  At this point in time, the character attributes at the current offset are for the non-bold character at the caret.  But, when the user starts typing, the character attributes will be bold.

We'd like to explore the idea of API that allows an assistive technology to query what the attributes will be for characters-to-be-inserted at the caret location, which is what we're calling the "insertion point."  This API should also support the case where the caret offset is at the end of the text (i.e., caretOffset == len(text)).
Comment 1 Li Yuan 2007-10-25 03:00:38 UTC
Can I say bug #487918 is part of this bug?
Comment 2 Willie Walker 2007-10-25 11:27:20 UTC
(In reply to comment #1)
> Can I say bug #487918 is part of this bug?
> 

Oops!  Sorry I forgot so quickly about that bug.  I think this bug obsoletes bug 487918.  Joanie - would you agree?
Comment 3 Joanmarie Diggs (IRC: joanie) 2007-10-25 13:26:49 UTC
Indeed.  (And I had forgotten about it as well.)
Comment 4 Willie Walker 2007-10-25 13:32:59 UTC
*** Bug 487918 has been marked as a duplicate of this bug. ***
Comment 5 Willie Walker 2008-06-02 21:11:21 UTC
Do we have enough information to move forward with this bug?
Comment 6 Willie Walker 2009-05-08 15:28:38 UTC
Li - I think this is going to require changes to AT-SPI first and then OOo next.  Is this something you think you can do for GNOME 2.27.x?
Comment 7 Li Yuan 2009-05-20 07:33:50 UTC
Sure. I prefer extend the definition of parameter, e.g. return attributes at "insertion point" when (offset == -1).
The empty slot of AtkText is very limited.

Suggestions?
Comment 8 Willie Walker 2009-05-20 12:34:12 UTC
(In reply to comment #7)
> Sure. I prefer extend the definition of parameter, e.g. return attributes at
> "insertion point" when (offset == -1).

This sounds perfect.  Thanks!
Comment 9 Li Yuan 2009-05-21 08:12:29 UTC
Created attachment 135070 [details] [review]
ATK patch
Comment 10 Li Yuan 2009-05-21 08:12:53 UTC
Created attachment 135071 [details] [review]
at-spi patch
Comment 11 Li Yuan 2009-05-21 08:18:33 UTC
I have filed bug #583415 for the gail change. But this should not block OOo.