Content
View differences
Updated by Oliver Günther about 1 year ago
**As** a User/Admin/everybody
**I want to** use the link to local URLs, application URLs, other other non-http(s) URLs that the browser supports
**so that** we can use it with existing DMS, and other local applications
**Examples:**
* Application URL schemes:
* vis://FE0E3D1D-9DC5-4931-BF6C-9E01216047A4/3/8326584
* dict://term lookup
* vscode://file/path/to/file
* • figma://
* element://vector/webapp/#/room/!ID
* tel://number
* sms://number
* facetime://number
<br>
**Acceptance criteria**
* Under Administration → System settings → General, add a new setting above 'Welcome block text':
* Label: "Allowed link protocols"
* Type: Text area input, one protocol per line, similar to the attachment whitelist
* Caption: "Allow these protocols to be rendered as links in work package descriptions, long text fields and comments. For example, tel: or element:".
* When not empty, use this allowlist when:
* Rendering Markdown in the backend
* Loading CKEditor, so that it uses that allowlist for new links
**Known limitations**
* How The autolinking from text rendering does not work reliably with these application schemes. You will need to use this the "Linking" feature of CKEditor in CKEditor
the toolbar
* Option 1: Type the scheme above and alternatively, use auto-linking. Note that the link will not be shown automatically in CKEditor, but only after saving (same as when typing a HTTPS URL)
* Option 2: Use the link toolbar item autolink hotkey of CKEditor to create a link with the custom protocol
: [https://ckeditor.com/docs/ckeditor5/latest/features/link.html#autolink-feature](https://ckeditor.com/docs/ckeditor5/latest/features/link.html#autolink-feature)
<br>
**Out of scope**
* Provide working links to `file://` local links, which all modern browsers block. The configuration will allow to whitelist them, but will be able to provide a working link
**I want to** use the link to local URLs, application URLs, other other non-http(s) URLs that the browser supports
**so that** we can use it with existing DMS, and other local applications
**Examples:**
* Application URL schemes:
* vis://FE0E3D1D-9DC5-4931-BF6C-9E01216047A4/3/8326584
* dict://term lookup
* vscode://file/path/to/file
* • figma://
* element://vector/webapp/#/room/!ID
* tel://number
* sms://number
* facetime://number
<br>
**Acceptance criteria**
* Under Administration → System settings → General, add a new setting above 'Welcome block text':
* Label: "Allowed link protocols"
* Type: Text area input, one protocol per line, similar to the attachment whitelist
* Caption: "Allow these protocols to be rendered as links in work package descriptions, long text fields and comments. For example, tel: or element:".
* When not empty, use this allowlist when:
* Rendering Markdown in the backend
* Loading CKEditor, so that it uses that allowlist for new links
**Known limitations**
* Option 2: Use the link toolbar item
<br>
* Provide working links to `file://` local links, which all modern browsers block. The configuration will allow to whitelist them, but will be able to provide a working link