The SL app did not fail with IE but failed in Google Chrome? Did IE also raise InitializedFailed event? Can you also add eventhandler for Initialized and see if FeatureLayer's InitializationFailure has a value? It's also good to use Fiddler or Firebug to know exactly where it failed during the webrequests.
There should not be any difference in behavior with different web browsers. I just wonder if you were accessing a layer that is secured and maybe different web browsers handle authentication differently - that is a possibility.
SL app did not fail in IE and Firefox, but failed in Google Chrome. IE and FF raise InitializedFailed. InitializationFailure is not null it contain exception (and it is correct as web response is invalid, it is not valid feature layer json). I have made some test with console javascript object (as Richard wrote).And I think problem is with console.log function. I have tried this in Chrome:(System.Windows.Browser.HtmlPage.Window.Eval("console.log") as System.Windows.Browser.ScriptObject).InvokeSelf(new object[] { "dummy message" });
and it throws the same exception.Looks like ESRI.ArcGIS.Client.Log is trying to write message in the same way and fails. Also I have created my javascript function and tried to invoke it.Javascript:
var testconsole = {
testlog : function(arg){
alert(arg);
}
}
SL:
(System.Windows.Browser.HtmlPage.Window.Eval("testconsole.testlog") as System.Windows.Browser.ScriptObject).InvokeSelf(new object[] { "dummy message" });
And it works fine. So SL fails to invoke only console.log, probalby a bug. However it is not good that exception is thrown by ESRI.ArcGIS.Client.Log during attempt to output debug information 😞