Alt-PgDn inserts glyph after moving to next spread
InDesign 16.0 x64
Normally (and on the MAC), the user can press Alt/Opt+PgDn to center the next spread on the screen.
This is now broken on Windows. At least on the 2 PC's I use, both of which are up to date on Windows and Creative Cloud.
What happens now is that when the Alt key is released, a glyph is inserted into the text. And this causes the display to jump back so the insertion point is visible on screen.
Of course, if I'm not currently editing inside a text frame, the glyph doesn't appear, because there's no place for it to go.
This new problem prevents me from using Alt-PgDn and Alt-PgUp to navigate one spread at a time while I'm editing. For some reason, InDesign processes the navigation command (when NumLock is OFF) and thenprocesses the same keystrokes as if the NumLock were ON.
Still a problem with Windows 11 and latest CC version. It is a major nuisance.
As Peter points out (below) it's made even more of a problem by the fact that there is no indication that InDesign is inserting characters at the text insertion point. When you use this command to page several spreads away from the insertion point, the "numbers" you are tapping on the number pad (3, which is PgUp, and 9, PgDn) are interpreted as ALT-CODES, that is, as extended ASCII characters, which are then silently inserted at the text cursor.
So you may inadvertently leave behind random glyphs wherever the insertion point happens to be at the time.
It's a difficult problem for many people to pin down and describe. Please don't interpret the lack of complaints as evidence that this isn't affecting thousands of Windows users.
Peter Hildebrandt commented
We need to use ALT+PgDn to step through books for editing, but unfortunately it inserts random characters at the insertion point when used. These random characters cause significant issues when we publish client's books, as they are often inserted after final manuscript proofreading are done and just before we go to print. Our clients are none too happy to find umlauts, section marks, and other weird artifacts strewn throughout their book which were simply caused by us reviewing the final output before print.
It's interesting that it doesn't always do this. Sometimes ALT+PgDn works properly, so it lulls you into thinking it isn't broken. Then it starts dropping characters in your file.
As another poster mentioned, it only happens on the PgDn on the Windows keypad with NumLock off.
Still a problem in version 17.1
Just to be perfectly clear, this behavior is occurring on PC's with the NumLock OFF (i.e., the number pad is in navigation mode).
This behavior is NOT happening on a Mac, where you can use Opt+PgDn while editing in a text frame, without entering random glyphs.