gjtorikian / gjtorikian/markdowntutorial.com
Autocomplete Removing Characters
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 606
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
On some occasions a sort of Autocomplete removes or changes characters.
The following instances have been observed:
| Test Step | Expected Result | Observed Behavior |
|---|---|---|
| Add Capital letter after a special character, such as # or [ | The letter is inserted and the character remains | The letter is inserted and the special character is replaced by a blank space |
| Add a line break | A line break is inserted and nothing else happens | A line break is inserted and the preceding character is removed |
| Add a line break in a list | A line break is inserted and nothing else happens | A line break is inserted and formatting is autocompleted to continue the list (i.e. indentation and * or numbering) |
These were observed on an Android in Google Chrome using Gboard. Gboard autocomplete and autocorrect are turned off.
The behavior could not be reproduces in different contexts, such as Google Keep, or this issue editor.
Info
Google Chrome 110.0.5481.64 (Official Build) (32-bit)
Revision 82293b013185775ae599e70e2a65e2070c2c4950-refs/branch-heads/5481_61@{#2}
OS Android 13; Pixel 4a Build/TQ1A.221205.011
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the three listed cases in the issue editor on Android 13 with Chrome and Gboard, then compare behavior with the other contexts mentioned. Done means capital letters preserve special characters, line breaks preserve preceding characters, and list formatting is not unexpectedly continued.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100