Re: [orca-list] Likely bug with Office Writer, was: Re: More on submitting Orca bugs
- From: Andy Borka <sonfire11 gmail com>
- To: orca-list gnome org
- Subject: Re: [orca-list] Likely bug with Office Writer, was: Re: More on submitting Orca bugs
- Date: Fri, 15 Feb 2019 20:30:30 -0500
After seeing this, I believe Word and Windows does the same thing. If I
have my cursor halfway through a line, then press SHIFT+DOWN, the
selection will wrap to end the selection on the next line just below the
start of the selection on the line above it. In fact, testing this while
I write this email, selecting from the word "I" in the first line by
pressing SHIFT+DOWN, takes the end of the selection just after the word
"press". It would be worth seeing what happens when using SHIFT+END on
the first line, then using SHIFT+DOWN.
On 2/15/19 12:23 PM, Joanmarie Diggs wrote:
Hey Christopher.
Responses inline.
On 2/15/19 11:55 AM, Christopher Gilland via orca-list wrote:
Are you saying that what's occuring is, when I shift down arrow, the
second line of text saying item 2 wouldn't get selected, yet, when I
select that first line with item one, somehow, It's actually selecting
the bullet on line two as well,
Correct.
even though shift down arrow should only
select that one line of text from item 1?
While I would agree with you, the LibreOffice folks might consider that
a feature rather than a bug. Visually, what happens is this:
* Control+Home places you just to the left of the "i" in item1. In other
words the caret is already past the bullet.
* Shift+Down selects one physical line of text, i.e. the start of the
selection is where the caret is; the end of the selection is
immediately below the caret. Thus everything is selected from "item1"
up to, but not including the "i" in "item2". That includes the bullet.
Whether or not this is how it should be is a matter of debate. But if
you don't like it, file a bug against LibreOffice. Note that this is not
an accessibility issue; this is the behavior one gets without Orca
running; Orca merely presents what is going on.
If so, then, I think I'm starting to follow, and yeah, Nimer, you'd be
right if that's truely the case. This is starting to sound to me more
like a Writer bug mostly instead of Orca.
Well, what you were reporting initially *was* an Orca bug which I've now
fixed.
--joanie
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]