That's a per-container change for containers that have the attribute. I noticed the issue after the core skins were changed a while back. I don't know what the cause is, and it may not the be at the crux of your issue, but I certainly haven't had to think about it since making the change.

Rob

Hi all,

A little more information.  The problem, at least for me, is a packet filter for HTTP on our corporate firewall.  The firewall is stripping some of the javascript code that the menu depends on.  Therefore, the browser is not able to render the menu functionality correctly for the changes implemented lately in that menu object.  If I disable the packet inspection and malicous code stripping on the firewall, it works fine.  However, most sites with AJAX work fine with the filter on and it does add another level of protection for the network, so I turned it back on.  I have found one other site that does not work with the packet filter on and it is not a DNN site.

When I have time, I will pull the view code of the rendered pages and do a compare on them to see what the firewall doesn't like.  I will get that information and post it back here.  I guess depending on how many people this impacts will deem whether a change needs to be made to the core with code the newer packet filters think is more friendly.

I did not try the hack posted previously but if it does resolve the issue, that would be a good short term fix for now.  I will let you know what I find.

Wallew