Closed Bug 20597 Opened 26 years ago Closed 26 years ago

[URL DISPATCHING] url in email message doesn't load in browser window if a browser isn't up.

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: mscott)

References

Details

(Whiteboard: [PDT+] fix in hand)

mscott, first, nice work on the URL dispatching. when I have a browser window open, it works like a charm. I know you know about this problem, but I thought I'd log a friendly bug against it, so you can mark any duplicates of this one.
Target Milestone: M13
*** Bug 21833 has been marked as a duplicate of this bug. ***
*** Bug 19585 has been marked as a duplicate of this bug. ***
*** Bug 18282 has been marked as a duplicate of this bug. ***
Target Milestone: M13 → M14
I suspect I'm not going to start working on this till m14.
Adding Alex to the cc list because he's interested in this bug too.
*** Bug 25165 has been marked as a duplicate of this bug. ***
Nominating for beta as I'm pretty sure this is a required feature. I'm actually real close to having a fix for this. I've written a nsIContentHandler component entirely in JS. It should work fine except there are two problems: 1) JS components that are in local files on the user's machine aren't properly given the right capabilities. So right now they can't access xpconnect objects. Shaver's going to send me a patch for this. 2) There's a problem with returning xpconnect objects to a JS component when the component was invoked from C++. jband's helping me work on this xpconnect bug.
Status: NEW → ASSIGNED
Keywords: beta1
PDT+
Whiteboard: [PDT+]
Making note that we also need this for links in the AIM conversation log. Please verify any fix you have in that case as well. Thanks!
Priority: P3 → P2
Sadly, the problem with a component implemented in JS that needed to get a dom object from xpconnect could not be solved. Jband and vidur both agree that it was way to hard. So I was unable to use my JS implementation of this component. Which is unfortunate because it only took a couple lines of JS to implement. Instead I've implemented it in C++. It's a bit of a bulky change but seems to be working well so far.
Whiteboard: [PDT+] → [PDT+] fix in hand
Now I really really do have a fix for this and will be checking it in tonight.
I just checked this in. Now, if you click on a link in messenger that requires a browser window and if you don't have one open already, we'll creat the new window and load the url! *yeah*
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
QA Contact: lchiang → laurel
OK using: 2000-02-15-09m14 commercial build NT 4.0 2000-02-15-09m14 commercial build mac OS 9.0 2000-02-15-09m14 mozilla build linux rh6.0
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.