We've just set the en-US defaults for mailto and calendar protocols for the upcoming major release of Firefox (release 3.0). They are being tracked in bug 413630.
The defaults will be:
mailto: Gmail, YahooMail, Windows Live Hotmail
calendar: Google Calendar, Yahoo Calendar, 30 boxes.
These should work internationally but of course for each locale we'll create and track bugs for changes on these defaults.
In doing the research and gathering some feedback from localizers worldwide there seems to be more choice for local webmail providers than web calendar providers. I guess the localization of calendar is not yet that popular.
If you feel we may have missed something major in the choice of these defaults, I'm open for feedback. :) And, as always, we can make changes for locales that offer local language and good user choice options.
"(note: you'll need a bugzilla account to follow that link)" <-- this isn't true at all, so you can just drop that part completely. :) -- Fixed, thanks Reed
Posted by: reed | January 23, 2008 at 11:59 PM
I’m probably missing some significant detail here that makes my comment moot, but — where’s Thunderbird?
Posted by: Laurens Holst | January 24, 2008 at 06:32 AM
Just created cs-CZ sibling to that bug, see bug #413833
Posted by: Tom | January 24, 2008 at 09:56 AM
Laurens, from the list it appears that this is referring only to online protocol handling and not client side applications.
Michal, is this right?
Otherwise, yes, Outlook, Outlook Express and Thunderbird (among others) should be on the list.
Posted by: Mark S | January 24, 2008 at 10:49 AM
I have never heard about the calendar protocol. Where can I read about it? Thanks.
Posted by: Christian | January 24, 2008 at 01:51 PM
Laurens and Mark S, Mark S is correct - protocol handling currently deals with web based protocols only, therefore Thunderbird etc don't apply
Christian: here is a good starting link to more information http://wiki.mozilla.org/Firefox3/ContentManagement:Handlers#Protocols
Posted by: michal berman | January 24, 2008 at 11:04 PM
If I understand it right, webcal isn't a transport protocol (it just uses regular HTTP) but a way of signaling that the resource is an iCal file, i.e. an alternative to Content-Type that is visible in the URL itself. This sounds like a hack - isn't it?
Posted by: Christian | January 25, 2008 at 05:25 AM