Caps don’t work on bullet lists (Whatsapp example)

App Store Reopened Typing & autocorrect Normal

Gòrg · iOS 27 · iPhone17 ·

Steps to reproduce

  1. Open Whatsapp App
  2. Open a Chat or a group chat
  3. Type somth
  4. Type an - followed by a blankspace
  5. Write something down on this item of the bullet list
  6. Hit enter to get a new bullet point
  7. Press Shift key
  8. 💣

What I expected

I expect to be able to use Shift key on a bullet point to set the First letter in Capital leters. I’d even expect it to be automatically set after hitting enter, to be honest.

What happened instead

When pressing the shift key very weird things happen.

Discussion

ilikered MOD ·
status → Open
ilikered MOD ·

Confirmed and can be reproduced at will.

efko DEV ·

@Gòrg WhatsApp handles Enter in a list by itself and doesn't show the keyboard the new line, so Shift thought the cursor was still right after the previous word and rewrote it, deleting through the bullet. That's also why every new bullet started lowercase. Fixed for the App Store update after 2.2.1: Shift on a bullet only touches what you typed on that line, and each new bullet starts with a capital.

efko DEV ·
status → Needs testing
ilikered MOD ·

Although the capitalization works for each bullet, there’s a leading space before every starting word at bullet.

ilikered MOD ·
status → Reopened
efko DEV ·

@ilikered on a new bullet WhatsApp still shows the keyboard the end of the previous line, so a swiped word or a picked suggestion thought it came right after that word and got a space in front. Fixed for build 465 (and the App Store update after 2.2.1): the first word on a bullet goes in without a space. If you were typing it letter by letter rather than swiping, tell me, that would be a different cause.

ilikered MOD ·

Yes, issue was with Swiped word/Picked Suggestion. Letter by letter typing doesn't insert that stray space. Will validate in 465.

efko DEV ·
status → Needs testing
ilikered MOD ·

Space issue is fixed for swiped words at bullet. However, picking a suggestion after the bullet breaks the bullet and messes up the format. Also the left most suggestion seems to keep append the typed words endlessly. See the attached video.

efko DEV ·

@ilikered on a new bullet the keyboard still read the end of the previous bullet as the word being typed, so a picked suggestion deleted that word (and the bullet with it), and the left suggestion glued the old words to the new letters. Fixed for build 466 (and the App Store update after 2.2.1): everything on a new bullet now only looks at what's typed on that bullet.

ilikered MOD ·
status → Reopened
efko DEV ·
status → Needs testing
ilikered MOD ·

Still not there fully.

efko DEV ·

@ilikered in your b466 video the first picked suggestion deleted 2 letters instead of 6 and the next one deleted 7. I can't explain both with one cause, and I've already guessed wrong three times. Inside a list WhatsApp tells the keyboard something different from what's on screen, so build 467 records what it actually sends. When you have 467, could you make a short list again (a few bullets, Enter, backspace up to an earlier bullet, pick a suggestion there) and send me the export from EF → Diagnostics? It only logs the shape of the text, letters show up as a/A, not your words.

ilikered MOD ·
status → Reopened
efko DEV ·
status → Needs info
ilikered MOD ·

Diagnostics attached.

efko DEV ·

@ilikered your export showed the cause: inside a list WhatsApp never tells the keyboard about the bullets it adds or removes, so after Enter the keyboard sees the new bullet glued to the end of the previous one and counts letters from that. What I can't see in the log is the screen. In build 468 the keyboard tries to make WhatsApp resend the real text right after Enter and logs whether it worked. Could you make the same short list in 468 again, this time with a screen recording running, and send both the video and the Diagnostics export from that same run?

ilikered MOD ·
status → Open
efko DEV ·
status → Needs info
ilikered MOD ·

Attached both.

efko DEV ·

@ilikered my mistake: the change I described didn't make it into 468, so this run behaved the same as 467 and the log has nothing new about the list. Your video still shows exactly the cases I need, like "meagmessage" and the bullet that fell apart after a picked suggestion. The experiment will be in build 469. When you have it, could you do the same short list once more with a recording and the Diagnostics export, ideally right after reopening the keyboard?

ilikered MOD ·
status → Open
efko DEV ·
status → Needs info
efko DEV ·
status → Open
efko DEV ·
status → Needs testing
ilikered MOD ·

Attached the video and diagnostics.

ilikered MOD ·
status → Reopened

Sign in to comment or vote.