All,

Just had an issue that was driving me up the wall. Basically, i had been making lots of code changes to quite a few modules and had been merrily working my way thro some enhancements. all of a sudden, when selecting anything on a DropDown list, the behaviour off all DropDowns were displaying erratic behaviour. Basically it seemed to perform the postback as the dropdown was invoked, rather than when selected. after pulling my hair out for over an hour, i decided to try it with a different theme selected (manually setting the default in the <pages theme in the web.config file as i couldn't select it in the app as it wouldn't work). lo and behold, it worked fine. this led me up a different track and decided to look at the recent default.css changes that i'd made in my preferred scheme. turns out, the only major addition i'd made that day, was the additon of a new class in the css file:

.highlight {text-decoration:none; font-weight:bold; color:black; background:yellow;}

so, i decided to remove this entry and try again. bl**dy h*ll, the problem was gone and all worked fine. i then renamed this class to .highlightsrc and tried again and it still worked as it should do.

so, basically, the essence of this tale is to beware tracking down bugs in code that could be attributed to 'non-code' related issue such as css definitions.

this is also an advance warning to anyone planning to allow users to define their own css files that once you do, then the control of what's added to that file is out of your hands and any possible error reports will be well and truly out of your hands.

i urge everyone to try the above example just so that i know that it isn't just me that this happens with (i tried it on 2 different machines with the same result)

anyway - older and definately wiser!!

jim

__________________
jimi

http://www.originaltalent.com

I assumed you were just crazy. I couldn't see anything in that css snipette that would make a drop down misbehave.

But damn!! It does just what you said.

There already is a css entry in the stock Default.css called highlight, so it must be some interference effect. I would have expected the system to throw an error.

On the other hand it could be that the gods of web design are offended by that gauche color scheme.

pat

http://weboperahouse.com

Pat,

you're probably quite right - thor was angered by the abomination of hi contrast and lo-fi taste :).

but just goes to show that such an oversight (on my part) of defining a duplicate attribute is the css can have catastrophic system-wide effect!! [cue thunderstorm].

cheers for now

jimi

Although Thor may well be displeased with the colour scheme it could be down to a less X-Files explination :)

BasePage calls a helpers method (on line 62 in my BasePage.cs file) - SetInputControlsHighlight and feeds in the "highlight" css class. The SetInputControlsHighlight method is in the Helpers class.