1282221 - A11Y AT-SPI non standart event for caret-moved (not including detail1 caret offset)

Status: RESOLVED INCOMPLETE

(Core :: Disability Access APIs, defect)

Description

[ksamak]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160607223741

Steps to reproduce:

developped focus tracking software in compiz. i fell on this issue, the text isn't followed correctly by screen magnifier in gecko related softs.
bug can be observed through accersizer, or dbus monitor.
Bug happens in firefox and icedove.



Actual results:

When moving through text, or writing text:
an "object:text-caret-moved" event is sent, according to AT-SPI and STK standard, but no "detail1" field is provided, which is supposed to carry along the caret offset in text.


Expected results:

The event should send along it's caret offset, so that the received AT-SPI event can find out the right offset.

Comment 1

[Marco Zehe (:MarcoZ)]

CC'ing Joanie and Trevor.

Comment 2

[Alex ARNAUD]

Dear Mozilla contributors,

I can reproduce the issue in GNOM3 environment (with the integrated GNOME Magnifier extension) (version 3.20.2) so it seems it's a general bug.
The strange thing is : when I add only one character (even escape) at the end of a line the problem disappear. 

Best regards.

Comment 3

[Alex ARNAUD]

(In reply to ksamak from comment #0)
> User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
> Firefox/45.0
> Build ID: 20160607223741
> 
> Steps to reproduce:
> 
> developped focus tracking software in compiz. i fell on this issue, the text
> isn't followed correctly by screen magnifier in gecko related softs.
> bug can be observed through accersizer, or dbus monitor.
> Bug happens in firefox and icedove.

Hello Ksamak,

Could you provide more reliable step-by-step process? If you want me to be able to confirm the issue I should be able to understand the way for the reproduction.

> Actual results:
> 
> When moving through text, or writing text:
> an "object:text-caret-moved" event is sent, according to AT-SPI and STK
> standard, but no "detail1" field is provided, which is supposed to carry
> along the caret offset in text.

Could you tell me what "detail1" is? Why is it useful for the screen magnifier? If it is not present how do you process ?

Cheers.

Comment 4

[Samuel Thibault]

Hello,

I couldn't reproduce the issue. For instance, while typing this very text, accerciser is getting object:text-caret-moved events with proper detail1 information, and while moving within the text as well.

Samuel

Comment 5

[Alex ARNAUD]

(In reply to Alex ARNAUD from comment #3)
> (In reply to ksamak from comment #0)
> > User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
> > Firefox/45.0
> > Build ID: 20160607223741
> > 
> > Steps to reproduce:
> > 
> > developped focus tracking software in compiz. i fell on this issue, the text
> > isn't followed correctly by screen magnifier in gecko related softs.
> > bug can be observed through accersizer, or dbus monitor.
> > Bug happens in firefox and icedove.
> 
> Hello Ksamak,
> 
> Could you provide more reliable step-by-step process? If you want me to be
> able to confirm the issue I should be able to understand the way for the
> reproduction.
> 
> > Actual results:
> > 
> > When moving through text, or writing text:
> > an "object:text-caret-moved" event is sent, according to AT-SPI and STK
> > standard, but no "detail1" field is provided, which is supposed to carry
> > along the caret offset in text.
> 
> Could you tell me what "detail1" is? Why is it useful for the screen
> magnifier? If it is not present how do you process ?
> 
> Cheers.

@Marco: I've submitted a NI request the 2017-07-27 to Ksamak without obtraining any answer after 1 year. We're not able to reproduce the issue.

I let you judge if we should keep this bug open but I see no reason to do that. As I've not the right to change the state it's only in your hand.

Best regards,
Alex.

Comment 6

[Marco Zehe (:MarcoZ)]

No answer in 1 year from reporter. Closing as INCOMPLETE. Feel free to reopen if new information becomes available.