[Bug]: Caps lock keeps !@#$ instead of 1234 in number row
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- mobile-dev
Research direction
No files are named in the report, so start by locating where the keyboard tracks shift and caps-lock state and where key output is computed for the number row. Reproduce first on a build of v4.3.5 by long-pressing shift, confirming letters capitalise while digits turn into symbols. Done means caps lock uppercases letters only, while a single shift still produces the symbol variant of the number keys.
Written by the indexing model from the issue text.
Description
Preliminary Verification
- I have searched existing open and closed issues and discussions to verify this bug is not already reported.
- I have tested or verified this behavior on the latest release or beta version.
- I have tried clearing app cache or testing with default settings.
- If the issue is related to an external plugin (e.g. Voice Plugin, OCR, CJK, Handwriting, Offline AI), I have verified that I am using the latest release of that plugin.
Description of the Bug
When using caps lock (not single shift), the digits are also shifted, which is not how it normally works.
That should only happen when shift is pressed one time, like a physical keyboard.
Steps to Reproduce
- Long press shift
- All letters get CAPS (which is correct), but digits also gets !@#$... instead of 1234...
Expected Behavior
When long press shift (CAPS LOCK) only letters should be UPPERCASE, but digits remain digits.
Logs / Crash Report
Build Flavor
Standard (with local AI, voice, and OCR support)
App Version
v4.3.5
Plugin Version (if applicable)
No response
Device & Android Version
Nothing 2a Android 14
Target App (if applicable)
Any
Screenshots or Screen Recordings
No response
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 59
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LeanBitLab/LeanType
-
Hebrew keyboard uses Arabic symbols layout (؟ instead of ?)Possibly taken @YiftahCooper claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
LeanBitLab/LeanType#882 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
LeanBitLab/LeanType#873 · 4 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
LeanBitLab/LeanType#872 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
LeanBitLab/LeanType#870 ·
Maintainers usually reply within 1 day
-
question
Difficulty 5/5 Over a week Newbie friendliness 12/100
LeanBitLab/LeanType#865 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in LeanBitLab/LeanType
Similar issues
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Heavy legs 1.12–1.17: compiler corpus goldens not regenerated for #4770Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
intellij-elixir/intellij-elixir#4782 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
komikku-app/komikku#1983 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Seb3thehacker/gearslip#121 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openapi-processor/openapi-processor-spring#524 ·
Maintainers usually reply within 2 days