Re: bug in browsemode

Brian's Mail list account

Is this the new 64 bit version of Firefox by any chance?

Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Martin Thomas Swaton" <list@...>
To: <>
Sent: Tuesday, October 03, 2017 4:38 PM
Subject: Re: [nvda] bug in browsemode

Hi once more

no I found out that there not even have to be special characters in the
non-linked-textblock and nvda still does ignore/skip some blocks.

currently I had a conversation that looked like that:

link name1


Just now
link name2

Just nowSent from Web
link name1


where textline 1 and 2 are read by pressing "n" and the "haha" block is
simply ignored allthough it is placed between two link lines.

I think this is not as expected.


Am 03.10.2017 um 00:19 schrieb Martin Thomas Swaton:

Am 03.10.2017 um 00:04 schrieb Quentin Christensen:
Just to clarify, is it treating the smiley emoticon as a graphc (and
therefore the text before is one nonlinked text element, then the
graphic element, then another nonlinked text element)?
no, it really is just text.
but I am not sure how consistent this behaves.

had the same with "hm..."
but only further down in the thread, when it got up in the thread it
was recognized as text (non linked)

so there might be a second trigger, that I could not figure out until now.

so fact is, if there are some special characters (not grafical items,
just text) it may be handled as something else than "not linked text".


On Tue, Oct 3, 2017 at 7:14 AM, Gene <gsasner@...
<mailto:gsasner@...>> wrote:

Also, n should not do two separate things, as you are asking.
How does n know what you want? You often intentionally want to
use n to skip to the next block of nonlink text if you don't want
to hear the block you have used the command to skip to. You can
make a case that, if you have already started speak all, that n
should skip to the next nonlink text and resume reading. But
having n skip to the next nonlink text and then, when pressed
again, read that entire block, is a very bad idea. N does one
thing and should do one thing, skip to the next nonlink text.
Whether continuous reading occurs after you skip may be offered
as the behavior when speak all has been executed before using n.
----- Original Message -----
*From:* Martin Thomas Swaton <mailto:list@...>
*Sent:* Monday, October 02, 2017 2:27 PM
*To:* <>
*Subject:* [nvda] bug in browsemode


I guess I discovered a bug in the behaviour of nvda in the

using the shortcut "n" to jump to the next unlinked text on a
does not work correctly when there are special characters in a
text line.

steps to reproduce:

e.g. go to m.facebook website -> messages -> friend-name

to open a thread.

in this thread you can jump to the text you and your friend wrote

if you type "*smile*"

or similar on a line

this line will be ignored by "n" and you will jump directly to
the next
"normal" textline.

This should absolutely not be the case, as you miss normal text
of this bug.

a second problem with "n" is, that not the whole text block is
read on
this keypress - but the next "n" press jumps to the next block of
and does not read the rest of the current block

because of this second block you always only hear the first line
of a
textblock when using "n"

so you cannot read a text with this shortcut, you only get the dirst
line of every block and then have to use other reading shortcuts
to read
on, which does not make any sense.

hope this two bugs can be confirmed and hopefully be fixed



Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now
available: <>
Twitter: @NVAccess

Join to automatically receive all group messages.