[Webkit-unassigned] [Bug 25669] New: [GTK] Incorrect/missing caret-moved events when navigating across object boundaries

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25669

           Summary: [GTK] Incorrect/missing caret-moved events when
                    navigating across object boundaries
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Accessibility
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joanmarie.diggs at gmail.com
                CC: xan.lopez at gmail.com, William.Walker at sun.com


Steps to reproduce:

1. Open the (to be) attached test case.

2. Enable monitoring of object:text-caret-moved events in Accerciser.

3. Position the caret to the left of the link in the test case and move forward
character by character using Right Arrow.

Expected results: When the caret is at the 'i' of the link 'is', a caret-moved
event would be emitted for the link with an offset of 0. Similarly, when the
caret is just past the 's' of the link 'is' (and is thus at the space of ' a
test'), a caret-moved event would be emitted for the text object ' a test' with
an offset of 0.

Actual results: When the caret is at the aforementioned positions, a
caret-moved event is issued for the object that had the caret, with an offset
of 1 + the previous offset. From Accerciser:

  object:text-caret-moved(4, 0, None)
        source: [text | This ]
  object:text-caret-moved(5, 0, None)
        source: [text | This ]     <-- caret at offset 0 of 'is'
  object:text-caret-moved(1, 0, None)
        source: [text | is]
  object:text-caret-moved(2, 0, None)
        source: [text | is]        <-- caret at offset 0 of ' a test'
  object:text-caret-moved(1, 0, None)
        source: [text |  a test.]

Note: It's not so much that the above events are incorrect as it is the events
for the new objects and offsets are missing. In other words, if it's easier to
continue to emit the events currently being emitted as a way to say "The caret
has left this object" but then follow those events with the requested events,
that's fine. If you want to replace the above events with the requested events,
that's fine too. :-) What's important is that:

1. We get the event for the new object and offset (because that lets ATs such
as Orca know what character needs to be spoken as well as presented as the
current character on the braille display).

2. If an AT asks for the caretOffset for an object which does not have the
caret, an offset that suggests this fact (e.g. -1 or the character count of
that object) is returned.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.