Enable Editing Text as soon as Text Box is in Focus

[jauyong]

Bug Description

The default rules for selecting and editing text are not applied as specified in figma

When a user adds text, they see the hint within the text box (fine):

But when they click within, they have to manually delete or overwrite this tip ("Double-click..."). Should the tip automatically "clear" when user clicks within the field?

Note: This issue does not deal with automatically enabling edit-mode when a new text field is added. This is only about being able to type while text box is in focus to edit content.

Reported by Claudio on #576

Expected Behaviour

1. You should be able to just start typing once the text box is in focus

Steps to Reproduce

Screenshots

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance Criteria

QA Instructions

Alphanumeric: Replace with new content

1. Add a text field
2. Unselect and reselect the text field using the mouse to make sure it has keyboard focus
3. Type any alphanumeric character and observe text field going into edit mode with only the typed character (NB: this only supports a-z and 0-9)

Enter: Select content

1. Add a text field
2. Unselect and reselect the text field using the mouse to make sure it has keyboard focus
3. Press enter and observe text field going into edit mode with all the currently present content selected and ready to be replaced by whatever is typed next. Also observe, that no actual newline is inserted despite pressing enter

[swissspidy]

Related: #1608

[csossi]

tested in QA Environment PR#2183

re: Instructions above

Alphanumeric: Replace with new content

1. Add a text field
2. Make sure it is selected
3. Type any alphanumeric character and observe text field going into edit mode with only the typed character (NB: this only supports a-z and 0-9)

Not working as described here. selected text element:

And when I began typing, it looked like this - just seeing a horizontal line:

[obetomuniz]

Hey @csossi, could you check it again using the PR#1810 env? At least, that's was the env that I addressed this issue, not PR#2183. Let me know if you have any doubt 😄

[csossi]

Verified in QA - thanks, @obetomuniz

[samitron7]

Verified in UAT