Automatic input of http:// in link field reduces usability

[John.K]

On CiviCRM profiles, where there is a website or link field, clicking into the field automatically inserts: http://
into the field.

I'm sure this is done with the best intention, but it is not good for usability. If someone clicks in to the field and then pastes a link, you end up with:
http://https://mysocialmedialink.com

The above (invalid URL) passes validation, whereas www.mysocialmedialink.com does not, giving the not-very-useful message: 'Enter a valid Website.'

Proposed changed

- Do not auto-fill the fields with http://
- Improve the validation error message to say 'Please include the http:// or https:// at the beginning of the URL'. Or something similar.

Next steps

I'd appreciate your feedback on this before I go ahead and create an issue in the tracker.

[JonGold]

Alternatively, validation could detect and strip out the double protocol specifier?  Though it's probably if it worked in reverse - don't add http:// until you're validating the field, and then validation can add it if it's missing.

[John.K]

I wondered about adding it in during the validation, but I wasn't sure about playing around with people's inputs too much like that. But I suppose, if it automatically entered http:// then the website itself would redirect to https if required.

[Dave Greenberg]

John - I agree that this is an annoying usability issue. How about removing the automatic input, and checking for http:// or https:// in the field validation. If missing, provide an improved validation error message.

[Fabian_SYSTOPIA]

On of our customers also had the problem when using copy & paste.

In addition, there are some restricted characters such as the German "Umlaute" (e.g. ü or ä). For a couple of years now those can be used in website urls however, the validation wouldn't accept it.

In short: +1 for removing the http:// autofill and or adapting it - if possible please also consider adapting the validation so it is less strict with special characters.

[John.K]

Thanks for the feedback everyone. I've created an issue here to take this forward: https://issues.civicrm.org/jira/browse/CRM-16531

[John.K]

There's an issue about umlauts specifically here, as it turns out:  https://issues.civicrm.org/jira/browse/CRM-15975

[Chris Burgess]

John - there's a fix already submitted for emails: CRM-16313. Some duplication between these three tickets?

* https://issues.civicrm.org/jira/browse/CRM-15975
* https://issues.civicrm.org/jira/browse/CRM-16313
* https://issues.civicrm.org/jira/browse/CRM-16531