I may be missing something, but I have one fundamental problem with the 'new search' which makes me continue to use the old one, and it has to do with placenames for place of birth.
It appears that you have to choose a place (country, county/state or town/village) from the drop-down menu and that if you go your own sweet way and type something in that isn't in the list, you'll get no search results. This was brought home to me especially because I happened to be searching for two particular problem locations at the time. One was Church Lawton in Cheshire. This is variously transcribed in full, or just Lawton, or Ch. Lawton. Only the full version appears in the menu, so only examples where the enumerator wrote the full name appear in the search results -- a very small proportion. If you enter either abbreviated form you get nothing, so you're reduced to searching the whole of Cheshire.
The other related to Waterfall, Staffordshire. This village is indisputably in Staffordshire but as it's in Ashbourne registration district, enumerators sometimes write 'Derbyshire'. But there's no way to search for 'Waterfall, Derbyshire', and because county and town are no longer separate, you can't just search for 'Waterfall'.
These problems all stem from genuine readings of what the enumerator clearly wrote -- I won't even go into the problems associated with mangled transcriptions or illegible writing. I'd also suggest that it's quicker to type in a placename and tab straight on to the next field than type the first few letters, then have to move your hand to the mouse to select the correct option from the menu, and then return to the keyboard to continue.
I'm at a loss to see how Ancestry think this is better than what went before.
