I tried it out locally, and it worked fine. I looked at the demo site, and it had mixed the address types up. The county selection is tied to the state selection of the same location type. (The reason for this is that if you had both home and work addresses on a form, you could select the home state and get the counties there and select a different work state and get the counties there.)
The default location type when you add a field to a profile is Primary, while the Name and Address profile that's the default for Drupal registration has all of its address fields for Home. If you add County real quick to the profile, it's probably County for the Primary location, while all the other fields are for Home. That's how it looked in the Drupal 6 demo site before I switched it to Home.
Unfortunately, some kind of caching is preventing the change I made on the demo site from taking effect, but I don't have any reason to believe it would act any differently than my local test.
I tried it out locally, and it worked fine. I looked at the demo site, and it had mixed the address types up. The county selection is tied to the state selection of the same location type. (The reason for this is that if you had both home and work addresses on a form, you could select the home state and get the counties there and select a different work state and get the counties there.)
The default location type when you add a field to a profile is Primary, while the Name and Address profile that's the default for Drupal registration has all of its address fields for Home. If you add County real quick to the profile, it's probably County for the Primary location, while all the other fields are for Home. That's how it looked in the Drupal 6 demo site before I switched it to Home.
Unfortunately, some kind of caching is preventing the change I made on the demo site from taking effect, but I don't have any reason to believe it would act any differently than my local test.