1) Create a mailto link with several parameters (address/subject/body etc.)
i.e. mailto:person@example.com?subject=RE:%20Email%20Subject&body=%0D%0A%0D%0A--%0D%0A%20message
2) Encode characters as needed (spaces to %20 line breaks to %0D%0A etc.)
3) Send this to a ProtonMail address.
4) Open the email in the ProtonMail client and hover over/click the link.
What is the expected result?
A new email should open in the composition window, with the expected fields already filled out, and the encoded characters parsed back into their original forms.
This same mailto link works as expected when sent to non-ProtonMail addresses and opened in other clients.
What happens instead?
In Firefox, hovering over the link shows in the link preview that the encoded spaces are parsed as space characters. In Edge, hovering over the link shows in the link preview the encoded spaces. In both, the line breaks remain shown as encoded in the preview. This may not be a ProtonMail issue and instead is a browser thing. I don't know.
Clicking on the mailto link opens up the composition window. In Edge, the fields are populated, but the encoded characters are not parsed and converted into their original forms.
In Firefox, the To field is populated with the address, but the subject and body are empty.
The Android client doesn't even seem to try. Clicking the link just opens up a completely blank email in the composition window.
What steps will reproduce the problem?
1) Create a mailto link with several parameters (address/subject/body etc.)
What is the expected result?
What happens instead?
In Firefox, the To field is populated with the address, but the subject and body are empty.