| Summary | New contact and disabled "name" field |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Bug |
| State | Assigned |
| Priority | 1. Low |
| Owners | Horde Developers, Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Requester | thomas (dot) jarosch (at) intra2net (dot) com |
| Created | 04/17/2008 (24 days ago) |
| Due | |
| Updated | 04/28/2008 (13 days ago) |
| Assigned | 04/28/2008 (13 days ago) |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch |
Assigned to
Assigned to Chuck Hagenbuch
Seems like a good system to me, though requires a bit more work to determine which are which. I'll work on it.How about showing the composite field (but not the component fields) on the display tab.. and showing the component fields (but not the composite fields) on the edit tab?> Is it possible to define a default field value for new contacts?
It is now. Unfortunately that doesn't completely solve the problem since the updating field is initialized onload, so even if you give 'name' a default value, it gets immediately wiped to '' once the form loads, since 'firstname' and 'lastname' are empty.
What about the idea of using CSS to make it not look like a form field?
Is it possible to define a default field value for new contacts?
The root of the problem is that the user does not really see that the form field is disabled as it's empty by default. If the field would contain something like "firstname lastname" and then gets cleared the first time a user types something in the firstname field, all would be fine.
> Not sure what tabs have to do with it?
If you use the optional 'tabs' entry in cfgSources, you can omit the 'name' attribute from any of the tabs so it will not display. I know it's not the best solution, but was offered as another option if nothing else would work. :)
Not sure what tabs have to do with it?
I modified Horde_Form_Renderer so that disabled variables are wrapped in a class="form-disabled". Can we work with that and CSS to make it look like text?
> I think the idea is to make it not a text field, right?
Yea, that makes sense, my bad :)
The idea about removing it from the display if your using a tabbed display is still an option though.
I think the idea is to make it not a text field, right?State ⇒ Feedback
Wouldn't it be more confusing for users to be able to type into a text field and have the value ignored or overwritten when the last/first name fields are edited?
You could always remove the 'name' field from display if it's really bothersome for your users.
Patch ⇒
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ New contact and disabled "name" field
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Hello together,
when you create a new contact, the first thing the user will try is to type in the "name" field, which is a composite of firstname, lastname and others.
The control is disabled and dynamically updated via Javascript.
Would it be possible to replace the disabled widget by text only
and still update it via Javascript? Other ideas?
Thomas