Before Aug 22, we need to make a decision how we should handle: <input> (no shortcuts) <textarea> (no shortcuts) <contenteditable> (currently displays shortcuts). We should decide whether we should: - disable shortcuts in <contenteditable> - if we have enough information on value, have some form of a compromise leaving it ON on a handful for a couple of websites.
Bug 1911631 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For Nightly 131, as a starting hypothesis, let's: **Remove shortcuts from:** <input> Keep existing shortcuts in: <textarea> <contenteditable> Once check grammar/improve tone prompt is ready, add it to: <textarea> <contenteditable> This is an interim state and we might change it based on our observations/user feedback.
For Nightly 131, as a starting hypothesis, let's: **Remove shortcuts from:** <input> **Keep existing shortcuts in:** <textarea> <contenteditable> **Once check grammar/improve tone prompt is ready, add it to:** <textarea> <contenteditable> This is an interim state and we might change it based on our observations/user feedback.