Answers.Body: <p>The Add/Edit custom field doesn't provide facility to add additional attributes but the Custom field table does have a column to store this attributes and this field is used while rendering the custom field. You can do this by any one of the method below</p>
  
  <ol>
  <li><p>Create a extension and use buildform() hook to add the attribute field on Add/Edit Custom field form. Once its added on the form after submit it will be automatically processed and stored in db by Civi.</p></li>
  <li><p>Once you have created the custom field you can use API explorer(CiviCRM >> Support >> Developer >> API Explorer) to update the attribute for a custom field as shown in below screenshot </p></li>
  </ol>
  
  <p><a href="https://i.sstatic.net/pRokc.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/pRokc.png" alt="enter image description here"></a></p>
  
  <blockquote>
    <p><strong>Note:</strong> Make sure you add space at the end for each attribute as this is concatenated with other attributes while rendering the field.</p>
  </blockquote>
  
  <p>Thanks</p>
  
  <p>Pradeep</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-11T05:00:05.443Z
Answers.Text: Thanks Pradeep. Your suggestion #1 is beyond my technical ability, but it gave me the idea to just go into the table and add "size=30 " (without the quotes but with the space after) to the attributes field for that custom field. It worked. Thanks again!
Answers.UserDisplayName: The Amateur
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-11T05:01:48.503Z
Answers.Text: So can we mark this as answered so that it will help others who will face similar problem
Answers.UserDisplayName: Pradeep Nayak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-11T05:12:19.153Z
Answers.Text: Yes, I think I did. Or maybe I don't understand how marking it as answered works.
Answers.UserDisplayName: The Amateur
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-10T11:12:09.623Z
Answers.LastActivityDate: 2019-01-10T11:12:09.623Z
Answers.UserDisplayName: Pradeep Nayak
Answers.Body: <p>I just use CSS to make the fields the width that I want. For instance: </p>
  
  <pre><code>#custom_92 { width: 236px; }
  </code></pre>
  
  <p>I just use the "inspect" feature on my web browser (Chrome: right click on an item, choose Inspect on the menu) to see the pixel width of the field I want to match to. Then I set it to be that same width in my CSS. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-11T05:09:44.707Z
Answers.Text: Thanks Jenni for taking the time to offer a solution. I am sure this would work. I didn't try it because, as I mentioned in my other comment, I worked out a solution involving a simple edit in the table.
Answers.UserDisplayName: The Amateur
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-10T03:35:20.880Z
Answers.LastActivityDate: 2019-01-10T03:35:20.880Z
Answers.UserDisplayName: Jenni Simonis
Body: <p>I have a profile that combines built-in fields with custom fields, both alphanumeric. The custom field displays shorter than the built-in fields which, when I examine the page source, are size="30".</p>
  
  <p>How can I set the display size of the custom field to match that of the built-in fields? I can't find a setting for it in the custom field edit area.</p>
  
  <p>Thanks.</p>
  
Tags: <custom-fields><profile>
Title: How do I set the display size for custom fields?
ThreadText: # How do I set the display size for custom fields?
  
  (Asked by: username_0 on 2019-01-09)
  
  I have a profile that combines built-in fields with custom fields, both alphanumeric. The custom field displays shorter than the built-in fields which, when I examine the page source, are size="30".
  
  How can I set the display size of the custom field to match that of the built-in fields? I can't find a setting for it in the custom field edit area.
  
  Thanks.
  
  **Tags:** custom-fields, profile
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-01-10. Score: 2 | Accepted answer
  
  The Add/Edit custom field doesn't provide facility to add additional attributes but the Custom field table does have a column to store this attributes and this field is used while rendering the custom field. You can do this by any one of the method below
  
  1. Create a extension and use buildform() hook to add the attribute field on Add/Edit Custom field form. Once its added on the form after submit it will be automatically processed and stored in db by Civi.
  2. Once you have created the custom field you can use API explorer(CiviCRM >> Support >> Developer >> API Explorer) to update the attribute for a custom field as shown in below screenshot
  
  [![enter image description here](https://i.sstatic.net/pRokc.png)](https://i.sstatic.net/pRokc.png)
  
  > **Note:** Make sure you add space at the end for each attribute as this is concatenated with other attributes while rendering the field.
  
  Thanks
  
  Pradeep
  
  > **Comments:**
  > **username_0**: Thanks Pradeep. Your suggestion #1 is beyond my technical ability, but it gave me the idea to just go into the table and add "size=30 " (without the quotes but with the space after) to the attributes field for that custom field. It worked. Thanks again!  
  > **username_1**: So can we mark this as answered so that it will help others who will face similar problem  
  > **username_0**: Yes, I think I did. Or maybe I don't understand how marking it as answered works.  
  
  ---
  
  ### Answer by username_2 on 2019-01-10. Score: 2
  
  I just use CSS to make the fields the width that I want. For instance: 
  #custom_92 { width: 236px; }
  
  I just use the "inspect" feature on my web browser (Chrome: right click on an item, choose Inspect on the menu) to see the pixel width of the field I want to match to. Then I set it to be that same width in my CSS.
  
  > **Comments:**
  > **username_0**: Thanks Jenni for taking the time to offer a solution. I am sure this would work. I didn't try it because, as I mentioned in my other comment, I worked out a solution involving a simple edit in the table.  
  
  ---
  
  