URL fields should not assume they're relative urls.
When a URL field is included in a table, it is displayed as a link, which is certainly handy - but unless the URL was entered with the protocol, http(s):// - it's rendered as a RELATIVE url, which I imagine will never be the intent.
I don't feel like I should have to populate https:// into the data when populating a url value, if I entered a domain name, google.com for example, I feel like I can reasonably expect it to link to https://google.com rather than https://app.nimble.com/google.com as it does presently.
3
votes
Will Vincent
shared this idea