On 8/14/2014 7:15 AM, bhargava.animes...@gmail.com wrote:
I am using gecko SDK 28.0 in my application. When my application is installed
in path having japanese/korean characters then in my embedded browser nothing
is shown.We found following error in logs
Could not read chrome manifest
'file:///C:/Users/an/Elements/main/build/targets/x64/elements2%C3%AF%C2%BE%C5%A0%C3%AF%C2%BD%C2%B7%C3%AF%C2%BE%E2%80%9E%C3%AF%C2%BD%C2%B6%C3%AF%C2%BD%C2%BD%C3%AF%C2%BE%C2%9D%C3%AF%C2%BD%C2%B6%C3%AF%C2%BD%C2%B7.Debug/mozilla/chrome.manifest'.
Could not read chrome manifest
'file:///C:/Users/an/Elements/main/build/targets/x64/elements2%EF%BE%8A%EF%BD%B7%EF%BE%84%EF%BD%B6%EF%BD%BD%EF%BE%9D%EF%BD%B6%EF%BD%B7.Debug/chrome.manifest'.
The actual path is
'file:///C:/Users/an/Elements/main/build/targets/x64/elements2ﾊｷﾄｶｽﾝｶｷ.Debug/chrome.manifest'.
Inside the browser complete white screen is shown. I have components that need
to be registered with chrome.manifest. Since i am getting this error , those
components would also be not registering .
This sounds like a bug, although it's not clear where exactly the bug is
without further debugging. Windows is especially hard in this regard
because the native codepage is variable and doesn't express the full
unicode range, so internally we try to use wide characters or UTF8 to
represent windows paths, but occasionally that fails.
You should file a bug to track the issue, but unless you can construct a
testcase where this bug affects Firefox, it's likely that you will need
to do the debugging yourself. cc me on the bug and I can point you to
the lines of code you should look at in your debugger.
--BDS
_______________________________________________
dev-embedding mailing list
dev-embedding@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-embedding
