[
https://issues.apache.org/jira/browse/GUACAMOLE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bradley Bennett updated GUACAMOLE-2217:
---------------------------------------
Attachment: image-2026-02-10-21-19-37-342.png
> Caps Lock not handled properly on Mac platforms
> -----------------------------------------------
>
> Key: GUACAMOLE-2217
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2217
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-common-js
> Affects Versions: 1.6.0
> Environment: Macintosh systems
> Reporter: Bradley Bennett
> Priority: Minor
> Attachments: image-2026-02-10-21-19-37-342.png
>
>
> {*}Lock keys{*}, such as {*}Caps Lock{*}, *toggle* the lock state between
> *off* and *on* each time the lock key is pressed. This differs from other
> {*}modifier keys{*}, such as *Ctrl* and {*}Shift{*}, where the state is *on*
> only while the key is held. In a browser, there is no way to directly query
> the state of a lock key; its state can only be determined from an input
> event, such as a key press, a mouse click, or a screen touch.
> Lock key input events are generated in one of two ways:
> # An event is generated on both the *press* and *release* of the lock key.
> # An event is generated only when the lock key is {*}pressed{*}.
> Apple hardware, such as Macintosh systems, fall into category 2.
> Caps Lock for category 2 systems is not handled properly. Examples of
> symptoms include:
> * *Caps Lock state* within the browser can be come *out of sync* with the
> actual Caps lock state.
> * The *Shift* modifier may become {*}inverted{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
