Suspect that the bug is also in the editing code that handles finding line boundaries.

Hey Leo, can you try to reproduce this? Thanks!

I'm able to reproduce the bug. While you can't read the current line in the menu using the standard commands, you can still achieve the same by having NVDA report the object in focus (NVDA+Tab). If pressed once, it reads the current menu item in focus. Pressing it twice spells it. This could be a temporary workaround.

For the comment above, I used the following version:
Version 68.0.3440.7 (Official Build) dev (64-bit)
JAWS Version 2018.1805.33 ILM
NVDA version 2018.1.1
Windows version 1709 (OS Build 16299.431

Changing the label to A11Y-q2-18 because it was found during our assessment.

I'm able to reproduce this, but NVDA is also reading "blank" when I press NVDA+up when focusing buttons in the toolbar, bookmark bar, or anything else in top Chrome. Is this happening for others?

Staging on kylixrd@ for Product Excellence phase.

Is NVDA+up supposed to read the item in the Chrome menu? The documentation says that it's supposed to "Read current line" but in the context of the "system caret," and there's no caret in menus. I verified that it works correctly in e.g. in the omnibox, where there is a caret. Like #12 says, NVDA+up also reads "blank" for many other things that don't have a caret.

Reading "blank" isn't super helpful, but we might have to live with it. Like #5 says you can use NVDA+tab to read it instead. I'm pretty sure we're tagging the menu items correctly, and there's no editable text to put the caret in, so I don't know what we would do to fix this...

cc nektar@, see comment #15.

Closing. Please reopen if there is actually action here.