Re: NVDA 2017.4rc3 released #nvdasr

Bhavya shah

Hi Brian,
Did someone already report issues with combo boxes on the web now? I
am particularly busy at the moment, so I cannot perform any amount of
comprehensive testing to determine the extent of this bug and to
verify whether or not it is a regression, but what I have been very
noticeably observing with NVDA 2017.4 RCs is that certain combo boxes
just cannot be opened. What I mean by this is that when I press Enter
on such a combo box, NVDA announces that it has expanded, but when I
arrow around, I continue traversing the document in browse mode and
the combo box is reported to have collapsed simultaneously. Alt+down
arrow or object navigation also fails in helping me reach the items of
such a combo box.
Unfortunately, I cannot recall which browser I was using while facing
this issue on more than one website.

On 12/1/17, Quentin Christensen <> wrote:
NVDA has several groups of pre-release versions, all publicly available

"Next" builds are "alpha" quality - new code gets added to these, which may
or may not work and may or may not ever make it to a stable version.

"Master" are "Beta" quality - once something has been in Next for a couple
of weeks and hasn't caused any issues, and it is felt it should be
considered for the next stable release of NVDA, then it goes into Master.

"Release Candidate" or "RC" builds and the final versions before the next
stable release. Essentially, once we release an RC build, if we don't find
any major issues with it, then the stable version will be released a week
or so later, which will be identical to that RC build, except for dropping
the "rc" part from the version number. If we do find an issue, then we'll
fix it one way or another and release a new RC build to ensure that
everything is working.

That snapshots page is always available and updated daily as new builds are
compiled (new Next builds might come out one or even several times a day,
Master usually every few days, and RC builds only just before a new stable
release is due - every three months). So essentially they are all public
betas, it's just that we publicise the RC builds more, to get more people
to try them to hopefully pick up any big issues before the final version.



On Fri, Dec 1, 2017 at 7:47 AM, Kevin Huber <> wrote:


So what is the difference between a release candidate and a public betqa?
Kevin Huber

On 11/30/17, Howard Traxler <> wrote:
And what is rc3? never saw this before.

----- Original Message -----
From: "Brian's Mail list account via Groups.Io"
To: <>
Sent: Thursday, November 30, 2017 8:56 AM
Subject: Re: [nvda] NVDA 2017.4rc3 released #NVDAsr

And there was one time when the release itself needed an update to

xxxx.x.x as well.

Sent via blueyonder.
Please address personal email to:-, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Rui Fontes" <>
To: <>
Sent: Thursday, November 30, 2017 12:07 PM
Subject: Re: [nvda] NVDA 2017.4rc3 released #NVDAsr

It is not the first time...

If I am not mistaken, once it have gone untill RC4...


Às 01:53 de 30/11/2017, Shaun Everiss escreveu:
Also I think this is the first time we have ever gone to rc3 its not

How close are we from release, I guess once there are no more bugs.

On 30/11/2017 1:47 p.m., Quentin Christensen wrote:
Hi everyone,

They say the best things come in threes and now NVDA 2017.4rc3 is
for testing! Coincidence? Probably, but in any case, this release
performance issues in applications such as MIRC which draw a lot of
text to
the screen. For the full details of what is new, and to download
build, head to:

Kind regards



Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
Twitter: @NVAccess
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons:

Contacting Me
E-mail Address:
Follow me on Twitter @BhavyaShah125 or
Mobile Number: +91 7506221750

Join to automatically receive all group messages.