Camino does not support the navigator.geolocation API, even though Firefox 3.6 (Gecko 1.9.2) does. * Browser geolocation test: http://benwerd.com/lab/geo.php
No one but Firefox is allowed to use Google's location provider, so I'm not sure how having that support is supposed to do anything without a provider. I imagine the back-end support is built and we just need to package an XPT to make that work (though again without a provider, not sure what good it would do), but we'd have to hook up support for listening for the site's request, showing a permission request to the user, and then add UI for changing/removing site permissions.
Sam argued in the channel the other day that we could write our own provider that wraps CoreLocation on 10.6 and thus at least have something for 10.6 users. I imagine the CL part is not hard at all (minus the lookup dance), but making it talk to Gecko is probably less fun. (We'd also probably get CL's request UI rather than anything we could manage/localize.)