716333 - get rid of WithConversion (xpconnect part)

Status: RESOLVED FIXED

(Core :: XPConnect, defect)

Description

[Makoto Kato [:m_kato]]

Attachment: fix

Comment 1

[Bobby Holley (:bholley)]

char*s are black boxes to the JS engine, so whether this patch is correct or not depends on where these strings come from, and whether those strings are UTF8, latin1, or something else. Have you done this analysis? Where do each of these strings originate?

Comment 2

[Makoto Kato [:m_kato]]

(In reply to Bobby Holley (:bholley) from comment #1)
> char*s are black boxes to the JS engine, so whether this patch is correct or
> not depends on where these strings come from, and whether those strings are
> UTF8, latin1, or something else. Have you done this analysis? Where do each
> of these strings originate?

Don't this return UTF-8 even if localized version?  If so, I should use NS_ConvertASCIItoUTF16 instead of.

Comment 3

[Bobby Holley (:bholley)]

(In reply to Makoto Kato from comment #2)
> Don't this return UTF-8 even if localized version?  If so, I should use
> NS_ConvertASCIItoUTF16 instead of.

I'm not quite sure what you mean. The issue here is that we need to know the original encoding of these strings in order to determine whether to use NS_ConvertUTF8toUTF16 or NS_ConvertASCIItoUTF16. The JS doesn't specify the encoding for JSErrorReport::filename, for example, so we have to track down where that comes from.

Comment 4

[Bobby Holley (:bholley)]

Comment on attachment 586769 [details] [diff] [review]
fix

Cancelling review until comment 3 is sorted out.

Comment 5

[Makoto Kato [:m_kato]]

Attachment: fix

Comment 6

[Makoto Kato [:m_kato]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/28cc6bf92f1f

Comment 7

[Matt Brubeck (:mbrubeck)]

https://hg.mozilla.org/mozilla-central/rev/28cc6bf92f1f