Since my name was brought up, I'll chime in (perhaps we can move these last few posts to their own thread for further discussion rather than hijacking this one?) -

I sent Mike a couple of things that might cause issues along with the code if this were implemented but figured that there would be enough intranet sites using it without form logins that it might be worthwhile (that and then I wouldn't have to redo the code changes when a new release was put out ;-).  In a purely intranet site with Active Directory there should be no need for form logins.

I'm using it in a major corporation with multiple domains but with logins being unique across the domains.  The domains are largely geography based and people have a tendancy to move around which means a change in domain.  Keeping the domain with the username would mean duplicate accounts for people when they moved which was the main reason why I made this change.  And of course the side benefit of being able to sort by username without the domain is helpful, too.