In a settings panel, pressing Apply should ensure that the current parameters are saved in memory. In Mag settings panel, it is not verified.
Steps to reproduce
- Start magnifier
- Open magnifier settings panel
- In the panel, modify zoom from 200% to 400%
- Press Apply
- Modify zoom from 400% to 100%
- Press Cancel button
Actual behavior
At the end, zoom level is at 200% (2x)
Expected behavior
Zoom level should be at the level when Apply was pressed, i.e. 400% (4x)
NVDA logs, crash dumps and other attachments
N/A
System configuration
NVDA installed/portable/running from source
Source
NVDA version
Last beta (commit ce19fa6)
Windows version
Windows 11 23H2 (AMD64) build 22631.6783
Name and version of other software in use when reproducing the issue
Other information about your system
Other questions
Does the issue still occur after restarting your computer?
Not tested
Have you tried any other versions of NVDA? If so, please report their behaviors
No, new code
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the System Accessibility Repair Tool in NVDA's tools menu?
Not tested
In a settings panel, pressing Apply should ensure that the current parameters are saved in memory. In Mag settings panel, it is not verified.
Steps to reproduce
Actual behavior
At the end, zoom level is at 200% (2x)
Expected behavior
Zoom level should be at the level when Apply was pressed, i.e. 400% (4x)
NVDA logs, crash dumps and other attachments
N/A
System configuration
NVDA installed/portable/running from source
Source
NVDA version
Last beta (commit ce19fa6)
Windows version
Windows 11 23H2 (AMD64) build 22631.6783
Name and version of other software in use when reproducing the issue
Other information about your system
Other questions
Does the issue still occur after restarting your computer?
Not tested
Have you tried any other versions of NVDA? If so, please report their behaviors
No, new code
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the System Accessibility Repair Tool in NVDA's tools menu?
Not tested