When I go to add a new article using the administrative page (AddEditArticle.aspx), all of the dropdown's act very strange, and quite annoying. When I select a dropdown, it immediately closes and the default value for that dropdown is not selected anymore. I then have to reselect the dropdown to open the list. I've noticed this problem debugging my own local copy and also on the DotNet2TheMax site (http://www.dotnet2themax.com/TheBeerHouse). Is anyone else seeing the issue I'm talking about and if so, what might be causing that behavior?

Thanks,

Doug

I'm trying to figure out where this behavior is located that you're talking about. When you select the control, initially, the drop down box will drop down exposing a list of items. If you mouse over an item in the box and select it the item is placed in the input box and the drop down box disappears. Is this the behavior you're experiencing? Or on initial selection the dropdown box opens and then closes, selecting the item under your mouse?

Further, where do you experience the problem? The body editor is an external 3rd party, albeit free, control.

Finally, I haven't set up my business web site yet, so the vb version of the web-site is still there. I have just tried the drop downs and the expected behavior works for me there using. You might try it there: http://www.mypcconnection.com

I get this too.
In admin mode: Manage Articles>Add New Article,
When you click the Category dropdownlist for the first time, the default category will disappear showing a blank entry. You then need to click on the dropdrownlist again to select a category ... somewhat irritating.
I didn't have chance to look into why but I was wondering if it was related to SetInputControlsHighlight since when the default text disappears, the dropdownlist becomes hightlighted.

Using both IE7 Beta 3 and Mozilla Firefox 1.5 I can't replicate the problem being described. Later today I will try with IE6.

Getting the same thing as well. I can confirm that it doesn't happen with Firefox 1.5.0.7 on Windows XP.
But it does happen with IE 6.

I think it is very likely to be related to 'SetInputControlsHighlight' because if I disable this (by commenting out the call to the Helper class in 'BasePage.cs') the problem disappears.

I suppose you could override the BasePage OnLoad event just for this one page to disable 'SetInputControlsHighlight'. But that would be a shame because it is a nice feature and would be good to have on all pages.

Did anyone find any other solutions?

Thanks

Holf