Closed Bug 200106 Opened 22 years ago Closed 22 years ago

supurious html-ing of words with colons on the end

Categories

(MailNews Core :: Composition, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 183111

People

(Reporter: peery, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 I had typed a moderately complex indented list in Composer, and sent it in both HTML and text to make sure that the recipients could read it nicely formatted. In two cases it took words with colons, and tried (wrongly) to turn them into links. Reproducible: Always Steps to Reproduce: Two instances follow: Text should have been: ------------------------ hosted: Cost for *400* Gb of data: * 2 database servers hosting 400Gb data, £9000 each(one live, one Generated HTML text was: -------------------------------- hosted:<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cost for *400* Gb of <a class="moz-txt-link-freetext" href="data:&nbsp;">data:&nbsp;</a> <br> <ul> Text should have been: ---------------------------------- and 7-9x in new data model which has known ineffiencies: Text was: --------------------------------- 7-9x in new data model which has known <a class="moz-txt-link-freetext" href="ineffiencies:&nbsp;&nbsp;&nbsp;">ineffiencies:&nbsp;&nbsp;&nbsp;</a> <br> <br> Expected Results: Mozilla should either 1) not try to html tags ending in colon except for specical cases 2) show me in the HTML message composition that it is going to do so, by displaying the text as green/whatever.
Already fixed a while ago. Will be in Mozilla 1.4a. *** This bug has been marked as a duplicate of 183111 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified dup and is fixed tested again with trunk build 20030422 on winxp macosx and linux
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.