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

Comments

yched’s picture

yched commented
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

aren cambre commented
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

bjaspan commented

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

bjaspan’s picture

bjaspan commented

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

aren cambre’s picture

aren cambre commented

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

yched’s picture

yched commented
Component: field system » javascript
Bojhan’s picture

Bojhan commented
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

aren cambre commented

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

Bojhan commented

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

aren cambre’s picture

aren cambre commented
Issue tags: -Needs screenshots

Removing tag because #8 sufficiently clarifies.

p.brouwers’s picture

p.brouwers commented
Status: Active » Needs review
StatusFileSize
new autocomplete.patch927 bytes

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

dries’s picture

dries commented

How to test this?

p.brouwers’s picture

p.brouwers commented

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

MichaelCole’s picture

MichaelCole commented

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

ff1’s picture

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

Bumping to D8...

kscheirer’s picture

kscheirer
Primary language English
Location Vallejo
commented
Issue tags: -Usability

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

Status: Needs review » Needs work

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

jpoirierpinto’s picture

jpoirierpinto commented
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.

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

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

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

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Needs work » Closed (outdated)

I tested this on Drupal 11.x, Umami install, today. When a nodereference autocomplete field gets focus, from clicking inside or tabbing to it, the field the entire contents of the autocomplete field is selected. This is not working as expected.