`tel:` URLs work incorrectly on Desktop

Bug Reports Closed
,
1

What’s The Bug?

On desktop, creating links that begin with tel: get incorrectly prepended with https://.

The tel: protocol (RFC 3966 - The tel URI for Telephone Numbers) lets you create links that open in your platform’s default dialer. This is very convenient for Android because it allows you to create clickable phone numbers that open the phone app.

How To Reproduce It

  1. Create a link
  2. Enter a phone number in the format tel:+1-555-5555
  3. Mouse over or click the link

Image or Video

tel url.png
tel url.png854×384 7.23 KB

The Expected Behavior

The phone number should not get prepended with https://, and should open the dialer when clicked.

Additional Context

tel: URLs work correctly on the Android version of Anytype.

Device

Macbook Pro 2023

OS

Somna 14.6.1

Anytype Version

0.43.2

Network Mode

AnySync

Technical Information

OS version: darwin arm64 14.6.1
App version: 0.43.2
Build number: build on 2024-10-29 18:28:47 +0000 UTC at #f582f2648d96d32f841c32eb59880315e30a8404 (dirty)
Library version: v0.36.5
Anytype Identity: A7NMHa5V7HUT5EEcbNsyZUT9v95sqV4Bg6ed2e36CA4NxZyo
Analytics ID: 943b038f-e1d0-47eb-98f3-3d8dda263144
Device ID: 12D3KooWQfN8KpCChs6mhCRp5yPbCPeGaoeT2t8ToAYAodQnYgwG

2

Use phone relation, you do not need a scheme for phone, it will be added automatically.

3

It’s a phone number I’ll have to call once as part of a task. Creating an object is excessive in this case, particularly because the document contains a half-dozen numbers. It would be like creating a new object for each http link in a document.

4

there is a relation with type “phone”

5

I have several phone numbers in a list without any semantic difference, having to create unique relations for each phone number doesn’t make much sense.

There are also other protocols that users might want to link in their documents as well, like magnet:, mailto:, irc:, ssh:, steam:, discord:, etc. It’s probably a good idea to just not add https:// if you detect another protocol spec.

6

This report has been added to our issue tracker and received by the Development Team.

8

Fixed

9

This issue has been fixed by the Development Team and will be implemented in an upcoming release.