291447 - When I try to use getUnicodeEncoder() or getUnicodeDecoder() then I get exception

Status: RESOLVED INACTIVE

(Core :: XPConnect, defect)

Description

[alexander :surkov (:asurkov)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0 (ax)

When I call nsICharsetConverterManager.getUnicodeEncoder() or
nsICharsetConverterManager.getUnicodeDecoder() methods then I get expception: 
Error: uncaught exception: [Exception... "Cannot find interface information for
parameter arg 1 [nsICharsetConverterManager.getUnicodeEncoder]"  nsresult:
"0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" ].

Can I use this methods from javascript?

Example:
var manager = Components.classes["@mozilla.org/charset-converter-manager;1"].
getService(Components.interfaces.nsICharsetConverterManager);

var encoder=manager.getUnicodeEncoder("windows-1251");

Reproducible: Always

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

nsIUnicodeEncoder is not scriptable. I would suggest using
nsIScriptableUnicodeConverter instead.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[alexander :surkov (:asurkov)]

Attachment: testcase

bug still presented. If this interface isn't reachable from javascript then I
guess exception should be some else.

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

so this bug is just that you want a different exception? -> xpconnect then

Comment 5

[clogged.drainpipe]

Is this issue still relevant? If not, it should be closed.

Comment 6

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.