- From: Murat Çorlu <notifications@github.com>
- Date: Mon, 20 Mar 2023 08:30:56 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/editing/issues/350/1476449623@github.com>
> How would that work for a textarea with existing text where I want to add a special character/emoji? I was considering just setting `inputMode` property via JS whenever needed, but I see the UX issues about returning to the previous `inputmode`. And I realized that native virtual keyboards don't allow to switch between inputmodes once we set it to `tel` for example. We need to have an event to track the user closed emoji picker so we can return back to previous inputmode. But if the proposed JS API will just show the virtual emoji keyboard on mobile (as suggested in https://github.com/w3c/editing/issues/350#issuecomment-1307519485) same UX problem stays there. How will the user close the emoji picker and return to the previous input mode? > For an addition into existing text the inputmode=text alteady does not exclude special characters. Adding an inputmode that does NOT allow for special characters could easily fall into a "discrimination" category. Because not all special characters are alike. `inputmode` is just for setting virtual keyboard. `inputmode=text` covers every type of textual input including numbers, decimals, phone number, urls... But still we have those input modes. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/350#issuecomment-1476449623 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/350/1476449623@github.com>
Received on Monday, 20 March 2023 15:31:08 UTC