Out of scope issues of status-im/status-react#10953
Some more findings and recapping earlier comments. I think all, except 1, should be addressed in a separate PR (bounty) if they are not regressions to text input in general. Functionality of receiving a notification when mentioned is more important
[ ] we should find a way to insert a @ character into the keyboard, at least on iOS where that's very common to have one next to space > STILL RELEVANT FOR IOS (Not sure it's possible on Android, can't find apps doing this)
[ ] the list could use an animation on change of states > STILL RELEVANT
[x] (image 1) on iOS jumping back to start of mention when completed. Expectation: cursor remains at end of mention name
[x] (image 2) on Android when entering first letter (e.g @f) to call mentions list, and successively selecting name from list, f is not replaced by name. Expectation: any character immediately following @ to be replaced by mention name
[x] (image 2) on Android own random name is shown in list while ENS name is connected to chat key.
[x] on Android when someone else mentions user A, and user A has ENS name, user A sees own name as e.g. hester.stateofus.eth, while other user see the name as e.g. @hester
[x] (original issue 1) (image 3) On iOS and Android, need to tap again on the text input field on list to make name a mention. Confirm without the additional tap to get the name right gives [:current "@hester"] Expectation: Manually enter name from list is parsed as mention name
[x] (original issue 2) On iOS Android, need to enter the first letter to pull up list to select name. Expecation: list appears on @ > STILL RELEVANT
[x] on Android and iOS tapping on a mentioned username should open the profile of the person rather than starting a new chat > STILL RELEVANT
[x] usernames block the long press gesture of a message bubble > WORKS NOW ON IOS AND ANDROID
[x] the list is using incorrect styling, bear in mind those aren't the regular list items components but a smaller custom one to fit more usernames into the list. > STILL RELEVANT
[x] the autosuggestion list is missing its drop shadow / elevation > STILL RELEVANT
Out of scope issues of status-im/status-react#10953
Some more findings and recapping earlier comments. I think all, except 1, should be addressed in a separate PR (bounty) if they are not regressions to text input in general. Functionality of receiving a notification when mentioned is more important
fis not replaced by name. Expectation: any character immediately following @ to be replaced by mention namehester.stateofus.eth, while other user see the name as e.g.@hesteragain on the text input fieldon list to make name a mention. Confirm without the additional tap to get the name right gives[:current "@hester"]Expectation: Manually enter name from list is parsed as mention nameiOSAndroid, need to enter the first letter to pull up list to select name. Expecation: list appears on@> STILL RELEVANT