Closed MattGyverLee closed 7 months ago
Oh, it looks like this was fixed 8 hours ago. https://github.com/keymanapp/keyman/pull/9901 You can close this bug if it's fixed.
This is a duplicate of a closed issue https://github.com/keymanapp/keyman/issues/9885
Describe the bug
I recently moved up to KM 17, and while "Test Keyboard on Web" works, the internal debugger that I was using in 16 can no longer be activated.
Reproduce the bug
You must include debug information to start the debugger. Check 'Include debug information' in the keyboard menu.
The internal debugger still has useful tools for dealing with dead keys and testing RALT sequences, so it would be nice if it returned to working.
Expected behavior
Debugging should load the debugger as it did in KM16 and not get stuck in a loop of enabling something that's already enabled. Can you reproduce this?
Related issues
No response
Keyman apps
Keyman version
worked in 16.0.141, failing in 17.0.198 and later (203).
Operating system
Win 11 Pro 22H2
Device
Windows Desktop
Target application
KmDev Debugger
Browser
No response
Keyboard name
sil_cameroon_qwerty, sil_tchad, presumably all of them as it appears to be a logic bug rather than a keyboard bug.
Keyboard version
No response
Language name
No response
Additional context
No response