Closed Bug 345307 Opened 19 years ago Closed 3 years ago

toString() conflict in nsIDOMLocation and java.lang.Object

Categories

(Core Graveyard :: Java to XPCOM Bridge, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: michal.ceresna, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060614 Fedora/1.5.0.4-1.2.fc5 Firefox/1.5.0.4 pango-text Build Identifier: The nsIDOMLocation interface defines a toString() method. Then in Java code: nsIDOMLocation loc=... loc.toString(); calls the java Object's toString() and there is no possibility to directly call the nsIDOMLocation's toString() method Reproducible: Always
This also applies to nsISelection.toString(). Is there a work around for getting the current selection in String form? I would think that this is an easy fix with the native code in the 'invoke' method, but I'm not familiar with the code there, nor have I built xulrunner/JavaXPCOM before.
Assignee: jhpedemonte → nobody
Product: Core → Core Graveyard

JavaXPCOM was removed in bug 648593.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.