Closed
Bug 435836
Opened 16 years ago
Closed 16 years ago
Exclamation mark at the end of a URL is not linkified
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: vargenau, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr-FR; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr-FR; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 With Firefox, you go page: http://en.wikipedia.org/wiki/Yahoo! In file menu, select "Send a link to page" This opens a compose window in Thunderbird. Thunderbird is configured to send mail in plain text. Send the mail. Read the mail and click on the link. The bug is that the link does not work because the exclamation mark is not made part of the link. (Well, in that precise case, you get the page as Wikipedia has a redirection, but that misses the point.) I do not know if the but is in Firefox or Thunderbird. Perhaps the link should be URL-encoded by Firefox. Reproducible: Always Steps to Reproduce: See above Actual Results: The link does not contain the "!" Expected Results: The link contains the "!"
Comment 1•16 years ago
|
||
I assume you are using TB 2.0.0.x? There no such problem in Thunderbird trunk at least TB3a1 works fine.
Comment 2•16 years ago
|
||
Confirmed with Thunderbird version 2.0.0.14 (20080421) Linux i686 — “!” at the end of a link is not wikified.
Product: Firefox → Thunderbird
QA Contact: general → general
Version: unspecified → 2.0
Updated•16 years ago
|
Summary: Cannot send an URL ending with exclamation mark → Exclamation mark at the end of a URL is not linkified
Reporter | ||
Comment 3•16 years ago
|
||
Yes, I use Thunderbird version 2.0.0.14 Sorry for not providing this information.
Comment 4•16 years ago
|
||
fixed on trunk therefore WFM
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
This bug is back at https://bugzilla.mozilla.org/show_bug.cgi?id=1379205 and there is discussion there about if/how to fix it again.
You need to log in
before you can comment on or make changes to this bug.
Description
•