[bug] URLs assumed to be http, ftp or file
turadg says:
In a message last June someone reported the bug that URLs were assumed to be HTTP (in "URLs assumed to be http"). The resolution from RTM was to add "file" and "ftp" support as well.
Well, there are more than three types of URLs out there. Why not support any URL? If you want to save people typing "http://" when it really is an HTTP url, then detect whether the field value is a valid URL first and don't auto-prepend on valid URLs.
My use case is that I want to use RTM to manage tasks related to mail messages in Mailplane (mailplane://) and Leopard Mail (message://)
Well, there are more than three types of URLs out there. Why not support any URL? If you want to save people typing "http://" when it really is an HTTP url, then detect whether the field value is a valid URL first and don't auto-prepend on valid URLs.
My use case is that I want to use RTM to manage tasks related to mail messages in Mailplane (mailplane://) and Leopard Mail (message://)