You can use these links to test various protocol handlers.
Mailto Protocol Testing
- Test 1: Open a compose window to noone@mozilla.org
Test Me!
- Test 2: Open a compose window to noone@mozilla.org, cc bob@mozilla.org, set
subject to "subject", and set body to "hello world"
Test Me!
- Test 3: Multiple To Addresses
Test Me!
- Test 4: Multiple Lines in Body
Test Me!
- Test 5: Invalid mailto URL - this should not work. Ideally there should be some sort of error message caused by this URL. Very few implementations tend to create such a message though.
Test Me!
- Test 6: Use a mailto and a to header - all addresses should be on To line. We have multiple permutations here. Because it is legal to specify both "to" and an "hname" whose value is "to" we have the following equivalences: mailto:addr1%2C%20addr2 == mailto:?to=addr1%2C%20addr2 == mailto:addr1?to=addr2. This tests all three permutations.
- Test 7: A mailto with embedded ampersands
Test Me!
- Test 8: A mailto with UTF-8 characters inside it. A picture of how this should look.
Test Me!
- Test 9: Negative Test: The From parameter in this message should be ignored.
Test Me!"
- Test 10: Negative Test: The Bcc parameter in this message should be ignored.
Test Me!
- Test 11: Unknown behavior: Some URL form encodings use '+' for a space, so we are throwing some tests in to see what happens when these are encountered in the mailto: URL. In my opinion, the encoded '+' should display in the mail. The unencoded '+' will probably fail in some interesting ways. However, my opinion is not the official word on how it should be handled.
Webcal Protocol Testing
- Test 1: Opens an event called Mozilla's 10th Birthday, on March 31, 2008 at 7PM.
Test Me!
- Test 2: Opens a very large web calendar.
Test Me!
