Re: [orca-list] Further to drive.google issues

[Joanmarie Diggs <jdiggs igalia com>]

Hey Nimer. Responses inline.

On 2/14/19 12:05 PM, Nimer Jaber wrote:

[...]
>     I definitely get brought to quick find. This is, again, with a
>     vanilla install on both Fedora and Ubuntu... so odd, wish I knew why
>     this was!!

Couldn't tell you. I don't think I have any special configuration
either. But I do know that when I hit / on a page that's not Drive, a
Firefox toolbar appears at the bottom of the window where I can type. In
contrast, when on Drive, the Drive search entry/combobox gets focus when
I press /.

> I did not use the Orca find. I thought this quick find was something
> built into Firefox?

It is. So is Ctrl+F. The difference is that the toolbar that pops up
when you use / just has an entry. The one you get when you press Ctrl+F
has widgets to move forward/backward, highlight all, match case, etc.

The reason I had mentioned what Orca does is not because it's Orca find,
but because stuff changes on screen, Orca gets events, and Orca presents
those events. What changes on screen is the search string gets
highlighted. So Orca waits for that event, and then reads the line so
that you can tell non-visually if that is the thing you were looking for
or not. This highlighting and subsequent presentation by Orca should
happen regardless of if you are in Firefox's quick find toolbar or
Firefox's find in page toolbar. And I mention all this because it sounds
a bit like what you were experiencing. In which case, I think Orca is
doing the right thing, but if you feel otherwise (i.e. Orca should not
be presenting the line when you use find in page or quick search), I'm
willing to listen. :)

> I would have wanted / to be caught by
> Google Drive, but it wasn't... or at least Orca announced quick find.

It sounds like it wasn't caught by Google Drive. The / key is not one
which is bound to any Orca command. Thus it just lets it pass through to
Firefox.

> By persists, I mean the state that it begins speaking and speaking
> persists after I clear search, thus making drive accessible again.
> Really have no idea why this is... I get this behavior with an incognito
> browser mode, as well as two different OS installs before any add-ons
> are installed...

Sorry for being dense, but are you saying that when you clear the search
"thus making drive accessible again" that interacting with Google Drive
works as expected and is presenting the correct information?

Lastly, would you mind making a tarball of your $HOME/.local/share/orca
file and emailing it to me privately? Just as a sanity check, I want to
replace my settings with yours to see if that makes a difference.
Because we're both using Fedora and Firefox without extensions and
you're getting very different and broken-sounding results.

Thanks!
--joanie