You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Web client creates shortcuts without protocol prefix (if not typed by the user), that leads to unexpected behaviours in other clients that expects the URL inside the shortcuts with http/https. Mobile clients can not open URLs in a browser if the URL has no http/https protocol
Steps to reproduce
New > Shortcut
Add URL without protocol prefix, like owncloud.com
Open shortcut in iOS client
Expected behavior
iOS client opens correctly the shortcut
Actual behavior
iOS can't open because the URL lacks of protocol
Actually, every client behaves in a different way:
Web: doesn't add protocol in creation phase
iOS: add protocol in creation phase
Android: initially, add protocol in creation phase (this is still under QA)
URL
The URL field is self-explanatory. It’s the address location of the page to load. It should be a fully qualifying URL with the format protocol://server/page. A URL file is not restricted to the HTTP protocol. In general, at least, whatever that can be saved as a favorite is a valid URL.
So, my suggestion is:
If user types the protocol in the URL, everything OK ✅
If not, adding https:// as default in creation phase
I agree with the default behaviour of adding https:// if the user didn't provide a protocol. 👍
Thanks for the feedback, we'll do in clients as well (iOS already does, Android will do), so that the URL will be formatted when the shortcut is created.
Describe the bug
Web client creates shortcuts without protocol prefix (if not typed by the user), that leads to unexpected behaviours in other clients that expects the URL inside the shortcuts with http/https. Mobile clients can not open URLs in a browser if the URL has no http/https protocol
Steps to reproduce
owncloud.com
Expected behavior
iOS client opens correctly the shortcut
Actual behavior
iOS can't open because the URL lacks of protocol
Actually, every client behaves in a different way:
As this unofficial format guide: https://www.lyberty.com/encyc/articles/tech/dot_url_format_-_an_unofficial_guide.html
So, my suggestion is:
https://
as default in creation phaseOpen to discussion with @felix-schwarz @Aitorbp @JuancaG05 @TheOneRing
The text was updated successfully, but these errors were encountered: