When a nodereference autocomplete field gets focus, from clicking inside or tabbing to it, the field the entire contents of the autocomplete field should be selected. This enables the user to replace the field contents simply by starting to type. That is easier than having to 1. click, 2. select all chars in the field, 3. type.

To provide the validity of this request, think about use of autocomplete field: if you're going to modify any portion, you will clear and start over, not just edit a few characters.

CommentFileSizeAuthor
#11 autocomplete.patch927 bytesp.brouwers
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch autocomplete_33.patch. Unable to apply patch. See the log in the details link for more information. View
Members fund testing for the Drupal project. Drupal Association Learn more

Comments

yched’s picture

Version: 7.x-2.x-dev » 6.x-2.x-dev
Status: Active » Closed (works as designed)

This is most probably not for CCK D7.
And this is in fact not for CCK at all, but for core's autocomplete feature.

Aren Cambre’s picture

Title: Nodereference autocomplete should have everything selected when clicked » Autocomplete should have everything selected when clicked
Project: Content Construction Kit (CCK) » Drupal core
Version: 6.x-2.x-dev » 7.x-dev
Component: nodereference.module » field system
Status: Closed (works as designed) » Active

Moving to core feature request.

bjaspan’s picture

This may be a good idea, but not if only one kind of form element does it.

bjaspan’s picture

... and thus I see no reason why it is specifically a Field API issue.

Aren Cambre’s picture

Thanks. Can you help me route this? I'm not sure where to put this issue.

yched’s picture

Component: field system » javascript
Bojhan’s picture

Issue tags: +Needs screenshots

Are we done moving it around :P? Lets get some screenshots up or demo to see its usefulness.

Aren Cambre’s picture

Demo: Open your favorite web browser, surf to a site, then click in the address field. The entire field becomes selected. You must click again to not select the entire field.

Bojhan’s picture

Ahh, thats clear language :) Sounds like a improvement that makes sense - I couldn't decipher the drupal language.

Aren Cambre’s picture

Issue tags: -Needs screenshots

Removing tag because #8 sufficiently clarifies.

p.brouwers’s picture

Status: Active » Needs review
FileSize
927 bytes
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch autocomplete_33.patch. Unable to apply patch. See the log in the details link for more information. View

Made a patch for this which will select the field when clicking inside the autocomplete field

Dries’s picture

How to test this?

p.brouwers’s picture

either manually of with a selenium test I guess, cause it's Javascript.

MichaelCole’s picture

#11: autocomplete.patch queued for re-testing.

ff1’s picture

Version: 7.x-dev » 8.x-dev

Bumping to D8...

kscheirer’s picture

Issue tags: -Usability

#11: autocomplete.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, autocomplete.patch, failed testing.

jpoirier-pinto’s picture

Issue summary: View changes
Issue tags: +Needs issue summary update

Is this still an issue?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.