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
TEST_DENY_ACCESS: - User is prompted again when they deny access, restart the machine and run Keyman.
Remove old version of Keyman after first removing its permissions from Security & Privacy > Privacy > Accessibility
Install the Keyman build for this PR
Restart the system
Select Keyman from the System Input Source menu
Confirm that dialog No. 1 is displayed.
Click the OK button and confirm that the System Preferences window is displayed with dialog No. 2 in the background
Do not enable accessibility access for Keyman
Restart the system.
Select Keyman from the System Input Source menu
Confirm that dialog No. 1 is displayed again.
Click the OK button and confirm that the System Preferences window is now displayed with Keyman unchecked for Accessibility (Dialog No. 2 may or may not be displayed in the background.)
In step 8. quoted from instructions in the second test of #7354 above, after restarting the system, Keyman triggers itself and the privacy alter text gets shown without users' action. With this said, step 9. is kind of unnecessary.
To Reproduce
Follow the steps above and try to observe the behavior after restarting at step 8.
Expected behavior
Keyman shouldn't trigger itself after denying and restarting the system with Keyman active prior to the restart.
Screenshots
N/A
Related issues
N/A
Keyman for Windows/macOS/Linux/iPhone/iPad/Android:
Device: MBP
OS: Big Sur 11.0.1 | Mojave 10.14
Keyman version: 16.0.70
Target Application: ?
The text was updated successfully, but these errors were encountered:
@mcdurdin I don't believe we want to do anything different in this case. If someone restarts when Keyman is active (although Privacy settings have not been enabled properly), then it makes sense after restart that the user would be notified to make the Privacy changes. We don't want them to start using Keyman without it functioning properly. I suggest we close this.
I agree -- if the user switches to Keyman, and at any point Keyman does not have the necessary permissions to function correctly, Keyman needs to make the user aware of this. Permissions get changed, by users, by OS upgrades, etc. The more self-healing that Keyman can be, the better!
Describe the bug
In step 8. quoted from instructions in the second test of #7354 above, after restarting the system, Keyman triggers itself and the privacy alter text gets shown without users' action. With this said, step 9. is kind of unnecessary.
To Reproduce
Follow the steps above and try to observe the behavior after restarting at step 8.
Expected behavior
Keyman shouldn't trigger itself after denying and restarting the system with Keyman active prior to the restart.
Screenshots
N/A
Related issues
N/A
Keyman for Windows/macOS/Linux/iPhone/iPad/Android:
Device: MBP
The text was updated successfully, but these errors were encountered: