Problem/Motivation
Quicksketch and I just spent 5 minutes talking about the new Placeholder form element on Field UI.
I asked him why he thought users would be allowed to define their own token names. Then he came over and read the description, and suggested maybe that field was some other kind of description, because surely the machine name would be the token name. Then we both read the description text on the Placeholder form element again, puzzled, and stared at each other for a bit. Then I blurted out "OH! Maybe its the pound-placeholder property on the form element!" I have a feeling I only arrived at that conclusion because I'm aware of the form API. But this won't help most end-users :)
The description even called it a hint, and quicksketch has a module called hint that does this exact thing, and we still couldn't figure out what this field did. :)
Proposed resolution
Update the description for the Placeholder field to describe it's behavior. How about:
Text that will be shown inside the field until a value is entered. This hint is usually a sample value or a brief description of the expected format.This is shorter than the current description, describes the behavior of a placeholder, and still uses the word 'hint'.
Remaining tasks
Update the description for the Placeholder field to describe it's behavior.
User interface changes
different help text
API changes
none
Related Issues
follow up to: #1241938: Add support for #placeholder to relevant Field API widgets
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| core-update_placeholder_description.patch | 7.43 KB | Idle | PASSED: [[SimpleTest]]: [MySQL] 52,182 pass(es). | View details | Re-test |