U4-3744 - Entire title is selected when trying to edit it

Created by Anders Burla Johansen 28 Nov 2013, 10:56:59 Updated by Murray Roke 30 Jul 2015, 06:33:34

Is duplicated by: U4-4516

Relates to: U4-4516

When you create a new node and then want to edit it at a later point - if you click the title/name text field then the entire text will be selected. Editors would like to most of the time just to correct a single char or a word. So default should be just to have the cursor where they click.


Niels Hartvig 28 Nov 2013, 11:13:18

It's by design that the whole text is selected (an increasing common practice). Keep feedback if you hear complaints about it, in practice it works quite well.

Anders Burla Johansen 29 Nov 2013, 08:45:26

Ahh okay - just tried it my self and thought it was not what I wanted it to do. But will let you know what our clients says

Bjarne Fyrstenborg 30 Jan 2014, 13:09:26

Perhaps a solution might be to use inspiration of Facebook search box at the top.. If to have entered some text in the textfield then first time you place the cursor in the textfield all text is hightlighted, but after that you still have the option to place the cursor at a specific position (second click i textfield).

Then all text would be hightlighted as default, but the editor still have the option to change e.g. a single character.

Phill Hodgkinson 30 Jan 2014, 18:10:01

I would agree this behaviour is very irritating. It works ok if you do everything by navigating with the keyboard, tabbing and arrow keys. However if you try to select specific word or letter using the mouse then it becomes irritating as it's not actually possible. Can you imagine if word processors worked like this, selecting a single character replaced your entire sentence? If you insist on this behaviour then I agree with Bjarne, that selecting all on initial click is ok as long as after you're able to select individual parts.

Bjarne Fyrstenborg 31 Jan 2014, 00:25:12

Another example is e.g. the URL address bar in e.g. Google Chrome. First click hightlight all text, second click position the cursor where you want.

Asbjørn Riis-Knudsen 24 Mar 2014, 20:47:52

Yes, if you want to have it select the whole title, you need to add the behavior described by Bjarne. Otherwise not having it auto-select is the better choice. Currently, it is impossible to use the mouse to place the cursor in the title if you're not using Chrome (which is the case for a lot of us!) I have been trying out Umbraco 7 with one of my clients and he was immediately frustrated by this. He was used to doing everything with the mouse and didn't even know how to navigate with the arrow keys in the textbox. This behavior is extremely user-unfriendly!

Asbjørn Riis-Knudsen 25 Mar 2014, 07:44:05

I'm going to see if I can implement the behavior described by Bjarne so that we can keep the current design, but make it easier to make edits. Hopefully a pull request should be coming up in a couple of days.

Asbjørn Riis-Knudsen 25 Mar 2014, 18:43:44

In this pull request I have implemented the behavior described by Bjarne. The text is still selected on first click, but subsequent clicks allow you to position the cursor and select freely. This seems a sensible compromise. https://github.com/umbraco/Umbraco-CMS/pull/332

Shannon Deminick 26 Mar 2014, 00:09:12


Murray Roke 30 Jul 2015, 06:33:34

I still find this frustrating (but I am not an end user, I'll ask around), I want the first click to position the cursor, perhaps distinguishing between a touch and a click, where a touch selects, and a click positions? alternatively some way to configure this? If someone could suggest how to get started writing a package to alter the behaviour that would also be great (if possible)

The Search & url-bar examples are not the same use-case. With these I often want to try something completely different, where as when editing a title I often want to make a small change.

I can't count the times I've overwritten my entire title when I simply want to append some words. It does not behave like any other input box on the page.

Priority: Normal

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category: Editor

Backwards Compatible: True

Fix Submitted: Pull request

Affected versions: 7.1.0, 7.0.4

Due in version: 7.1.0


Story Points: