Comment 1 by jteh on 2013-06-05 20:08
Because this is an edit combo box, NVDA removes the name from the edit field and only uses the name on the combo box. Otherwise, the label would be reported twice. Unfortunately, when tethered to review, you don't see context, so you don't see the combo box name. I'm not sure how to solve this.

Btw, this is another reason that only showing the focus when tethered to focus (rather than showing the context to the left) is problematic.

Comment 2 by halim on 2013-06-06 06:12
Sorry I can't agree. Showing the whole context at the left side has many disadvantages.

• In most cases a user knows which dlg which window, which app is focused. Writing this in every output doesn't make sense to me.
• because of different length in braillecontext information a braille user has to move his finger arround every time to find the wanted info. that info starts some times at pos 60 on a 80 cell brailledisplay.
• Maybe a dedicated braille command to display the context braille stuff would be enough!

Sorry this was a bit OT now!
Back to this ticket :-).
It would be nice if the label could be displayed in those edit fields. Unfortunately I need more time to read and understand the braille code. So I've no idea how to do this at this time..

Comment 3 by jteh (in reply to comment 2) on 2013-06-06 06:36
Replying to halim:

Sorry I can't agree. Showing the whole context at the left side has many disadvantages.

That may be, but the point is that you do lose combo boxes, for example, which is related to this ticket. You would see the same problem when tethered to focus that you see when tethered to review.

I know development has been going on in the Braille area, any comments or suggestions for this issue? CC @LeonarddeR

@LeonarddeR any thoughts on this issue?

@halim is this issue still reproducible?

@dkager could you please test with a braille display the current behavior in NVDA 2019.1.1? I guess with the automatic tetering of the braille display this should not be an issue anymore. But I do not have a braille display at hand to assess this.

This is still reproducible in Windows 10 with NVDA 2019.1.1. However, the point made in #3264 (comment) is still valid. I'm not sure how to resolve this issue and frankly, I would say this has low priority.