I have a site running ActiveProfile (precursor to ActiveSocial, sort of) that makes use of the DNN ClientAPI with a call to GetCallbackEventReference.

All is well with Firefox and IE, yet something breaks in Chrome and Safari. What breaks is the click event of a search button such as this - btnSearch.Attributes.Add("onclick", "dnn.setVar ('mode', 'search');" & DotNetNuke.UI.Utilities.ClientAPI.GetCallbackEventReference(Me, "'Find'", "NewSearchResults", "this", "SearcherrorFunc", "SearchstatusFunc", DotNetNuke.UI.Utilities.ClientAPI.DNNVARIABLE_CONTROLID) & "; return false")

Is it a browser issue similar to what's talked about here http://www.dotnetnuke.com/Resources/F... ?

Or maybe a ClientAPICaps.config issue similar to what's talked about here http://www.dotnetnuke.com/Resources/F... ?

Any advise would be greatly appredciated.

---

Eric Swanzey
www.swanzey.com

Thanks and yeah, I shoulda' mentioned - it's v4.9.5.

Just for kicks, we did various DNN upgrades to major version steps all the way through v6 but no change.

I wonder whether it's a WebKit thing, as that's the engine in common, but really am at a dead end.

---

Eric Swanzey
www.swanzey.com