You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by jhomme on 2013-06-20 13:53
In Microsoft Word 2010, the following happens.
Create a document with a line of text and make sure the speaking of style names is turned on.
Press any of these keys: Alt + Control + 1, Alt + Control + 2, Alt + Control + 3, Alt + Shift + Left Arrow, Alt + Shift + Right Arrow, Control + Shift + N, Control + Shift + L, etc.
Immediately press NVDA + F.
Expected: NVDA should say the new style name, because it has changed. What actually happens is that NVDA speaks the style name the text was formerly associated with.
Use any method you wish to move off of the line and back on, and press NVDA + F. NVDA now speaks the new style name.
It would even be better if NVDA would speak the new style name after the keys are pressed, but maybe that would be done only if style names are on. This would save the time of checking with NVDA + F, becausethe other information would have to be heard or interrupted.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2013-06-21 00:31
As I understand it, unless text is selected, pressing those keys doesn't change the style of existing text. Rather, it changes the style for new text after this point. NVDA+f reports the formatting info for the text at the cursor, so what it is doing here is correct.
Please provide further info if I've misunderstood and/or am mistaken in some way.
I just performed these steps in Microsoft Word 2016 with styles was selected in document formatting and was not able to replicate this issue. I think @jcsteh is right in #3294 (comment), that the performing those commands does not change the style of the text unless text is selected. Closing as worksforme
Reported by jhomme on 2013-06-20 13:53
In Microsoft Word 2010, the following happens.
The text was updated successfully, but these errors were encountered: