GNOME Bugzilla – Bug 538062
[blocked] Orca should announce when a placeholder is being moved on an Impress slide
Last modified: 2018-02-14 14:52:50 UTC
Steps to reproduce: 1. Launch Impress and create a new presentation. 2. Create a slide with title and text placeholders 3. Press F6 until you get to the scroll pane. 4. Tab to the first placeholder but do NOT press Enter to start editing. 5. Press one of the arrow keys instead. Expected results: Orca would say something* to let you know that you're moving the placeholder around. Actual results: Orca says nothing. (Which in my experience causes the user, who forgot to press Enter, to arrow around some more trying to find the text in that placeholder.) *Mike and I talked about what "something" is. We didn't come up with the exact string. But generally speaking, we want to know the direction, the amount moved if possible, and if the placeholder is now overlapping another placeholder as a result. Mike will need to spec this out, but maybe something along the lines of: * "Placeholder moved down 10 <units>" (where units is pixels or mm or inches or whatever we can get) * "Placeholder moved down 10 <units> and overlaps text placeholder" (maybe we also want to indicate where the overlap is taking place)
Created attachment 112707 [details] Orca debug log generated whilst testing this problem. We are getting absolutely no events as we press Right arrow to move the placeholder around (see the end of the attached debug log). I'll file YAOOOB and block this one against it.
OOo issue #90713 http://www.openoffice.org/issues/show_bug.cgi?id=90713 has been filed. Blocking this bug.
*** Bug 526997 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > OOo issue #90713 > http://www.openoffice.org/issues/show_bug.cgi?id=90713 > has been filed. The OOo team has marked this one as WORKSFORME, so I'm unblocking this bug and marking it as [to verify].
Removing the '[to verify]' for now. Here's the WORKSFORME comment: ~~~~~~~~~ When looking at accerciser I got 2 events object:visible-data-changed(0, 0, None) source: [list item | ImpressTitle 2] application: [application | soffice] and object:bounds-changed when moving a control with the arrow keys. I tested a OOo DEV300m57 Linux version. ~~~~~~~~~ The problem with the above is that we don't listen for either of the two events mentioned. We will persist in our refusal to listen for object:bounds-changed events because certain components of the GNOME desktop emit multiple instances of this event every single second. If we start listening for them, Orca users will experience a significant performance hit. :-( The question that remains is can/should we start listening for object:visible-data-changed? And, to be honest, I don't know yet. So I'm assigning this one to myself for now with the intent of at least answering that question. If the answer winds up being 'yes' then I'll see what I can do to implement the feature requested in this bug; otherwise, I'll re-open the original bug which was blocking us. Aiming for 2.31.2.
In my last test, this issue still appear in latest Orca version or I've miss understood the bug description. It should great if this bug could be solved. Best regards.
I still need to figure out what all we need fixed in LibreOffice. We don't need open Orca bugs for bugs which are not Orca bugs.
(In reply to Joanmarie Diggs (IRC: joanie) from comment #7) > I still need to figure out what all we need fixed in LibreOffice. We don't > need open Orca bugs for bugs which are not Orca bugs. Thanks for the explanation. What do we need on the LibreOffice side to make this working? Is there already a reported bug for that? Best regards.
(In reply to Alex ARNAUD from comment #8) > (In reply to Joanmarie Diggs (IRC: joanie) from comment #7) > > I still need to figure out what all we need fixed in LibreOffice. We don't > > need open Orca bugs for bugs which are not Orca bugs. > > Thanks for the explanation. What do we need on the LibreOffice side to make > this working? Is there already a reported bug for that? If you read the text you quoted, namely, "I still need to figure out what all we need fixed in LibreOffice" you'll note that I've not yet figured it out. Because I've not yet figured it out, I cannot file the necessary bugs.