Thanks for the report. That code was backed out in [6268] because of the bug reported in #4017. Were you seeing the ActiveX warning as well?

I was not seeing any ActiveX warning. The Cisco VPN client is likely to blame for a couple of reasons. First, it basically reads all javascript served through the VPN and replaces (very cleverly I might add) all calls to functions involved in DOM manipulations to run though it's own proxy functions. The issue was that as it basically funnels DOM manipulations through its own functions so that it can revamp any href or src attributes with the re-adjusted VPN url's. To do this, it parses any html strings injected into the DOM. As the jquery support object injects that dummy html string into the DOM to detect browser behaviors, the Cisco parser assumes that any param tags will have a name attribute. They should probably detect the presence of such attributes, but their scripts that are injected are hard coded in their firmware. The scripts (unfortunately) assume that any param tag will have a name attribute and subsequently cause a runtime error during the jquery loading process, thus rendering the site jquery-less. Simply adding the empty name attribute rectifies this problem. I know it is debatable as to whether this is a cisco issue or a jquery issue, but I think that the simple answer is that it may be both. The param tag *requires* the name attribute. In the interim, we have modified the jquery source files by simply adding an empty param attribute with a value of empty string to alleviate the loading problem. Any help is appreciated on this issue. Thanks in advance,

-Mark

I think this will be fixed in 1.3.2 by virtue of the patch mentioned above, so your local patch should hold you until then. I've noted this ticket in #4017 in case the code makes a reappearance in the future.

Duh, 1.3.3.

Hi,

I always have the same problem even after i had made the change!!

any idea?

Fixed by removing the code.