If you are in single document mode, then yes, this is a new bug. I’m not on 3.1.5.1, so I cannot test it.
But if you are in Scrivenings mode, then this is a known issue for Windows Scrivener, which has always worked this way in Scrivenings mode. It’s been discussed previously in a number of threads, particularly this one.
Yes it is. So irritating in fact that I wrote this small Autohotkey script to work around it:
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
#Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
;--------------------------------------------------------------------------
SetTitleMatchMode, 2
; #IfWinActive, Scrivener
; #IfWinActive ahk_class Qt51511QWindowIcon
#IfWinActive ahk_class Qt51514QWindowIcon
;--------------------------------------------------------------------------
^PgDn:: ; Ctrl+PageDown
Send {Down 13}
return
^PgUp:: ; Ctrl+PageUp
Send {Up 13}
return
It sets Ctrl+Page Up/Page Down to move the editor a predefined number of lines up or down.
Best,
Jim