Closed Bug 12117 Opened 25 years ago Closed 25 years ago

REMINDER: Review URL auto detection in libmime

Categories

(MailNews Core :: MIME, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rhp, Assigned: rhp)

References

Details

Do final review before production release.
Status: NEW → ASSIGNED
Target Milestone: M12
Need to deal with this after sabbatical.

- rhp
OS: Windows NT → All
Hardware: PC → All
Blocks: 11091
(target milestone is M11 or M12 - add to mail beta tracking bug)
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Actually took care of this one before I left on sabbatical. For details, send
me an email.

- rhp
QA Contact: lchiang → ppandit
Rich -

I can't find within CVS Query Tool which of your changes are involved with this 
bug. Can you tell me how to verify or show me the code changes so I can visually 
verify.

Thx,
Par
I have no idea, what this bug is about. Should I?
ppandit: FYI: I wrote the current URL detection code.
I am verifying this bug based on

1) The code has been rewritten by another developer (BenB)
2) This bug was about being able to detect instant messenger URLs
3) This bug is old and no one has complained about it or updated it

Please reopen if needed.
Status: RESOLVED → VERIFIED
That didn't take long. After emailing with Ben, I am going to reopen and let 
the developers mark this fixed after they are sure that AIM urls actually work.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
This has been fixed by a general solution for handling URL detection. I don't 
think there is an AIM url handler and I don't want this on my bug list while I 
wait for one to be developed. 

- rhp
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Rich - is there a testcase for this? Are all issues resolved?

Par
This was an internal thing that has been taken care of. :-)

- rhp
Based on rhp comments, marking as verified
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.