I recently did a trial upgrade of a copy of my production site www.AgingSafely.com on my localhost so see what issues came up. I had to make considerable changes to the "Master Reset" in my skin's skin.css file, as expected.  While testing the site with these changes, I was "clicking" the checkboxes in my search form an noticed that I was getting the WRONG number of record returned for the combination of boxes checked.  It "looked" as if I was one Ajax request for a new "MS SQL Select" behind current state of what was checked on the complex form! This problem was visible with FireFox, IE,and Chrome -- while Safari got the same results with both DNN6 and DNN7.

All of the code worked on DNN6.1.5 and failed the minute that the DNN7.0.4 upgrade was done.  The problem was troubleshot by a friend who said that with DNN7
"I added a breakpoint into the code in your uncheck function, as well as the ows.Fetch function in the new site. At the breakpoint I executed "jQuery('[name=fltAFH]').is(':checked')", which returned "false". This is contrary to what happens on your DNN6.1.5 site, as it returns "true" when the onclick was fired. The reason you are seeing this issue only in certain browsers is due to the order of handling of the event. jQuery is apparently overriding the onclick behavior, and causing it to operate in ECMA standards, which is - onClick occurs at the moment an element is clicked, where onchange is fired at the moment a form element value is changed."

I was able to "fix" the problem, by changing all  "onclick" event to "onchange" events.

Is this change in behavior between DNN6 and DNN7 expected, or a bug?

/Dave Snow