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
On macOS, within certain (but random) applications, the Serbian keyboard layout (both Cyrillic and Latin) fails to switch to any other layout. This issue occurs intermittently and affects the functionality of switching between different keyboard layouts.
Steps to Reproduce:
Install the Serbian - Cyrillic.bundle and Serbian - Latin.bundle layouts.
Remove any other layout.
Open a specific application (I was able to reproduce it in Safari and App Store apps).
Attempt to switch from the Serbian layout to another keyboard layout.
Observe that the layout does not change.
Expected Behavior:
The keyboard layout should switch seamlessly to another selected layout.
Actual Behavior:
The keyboard layout remains stuck on either "U.S. - Serbian" or "Russian - Serbian" layout, not switching to any other.
Environment:
macOS version: 14.5 (23F79)
Keyboard Layouts: Serbian - Cyrillic.bundle, Serbian - Latin.bundle
Note
If anyone knows the cause of this issue, please share your insights. I will try to fix it if possible.
The text was updated successfully, but these errors were encountered:
On macOS, within certain (but random) applications, the Serbian keyboard layout (both Cyrillic and Latin) fails to switch to any other layout. This issue occurs intermittently and affects the functionality of switching between different keyboard layouts.
Steps to Reproduce:
Expected Behavior:
The keyboard layout should switch seamlessly to another selected layout.
Actual Behavior:
The keyboard layout remains stuck on either "U.S. - Serbian" or "Russian - Serbian" layout, not switching to any other.
Environment:
macOS version: 14.5 (23F79)
Keyboard Layouts: Serbian - Cyrillic.bundle, Serbian - Latin.bundle
Note
If anyone knows the cause of this issue, please share your insights. I will try to fix it if possible.
The text was updated successfully, but these errors were encountered: