Closed
Bug 242652
Opened 21 years ago
Closed 20 years ago
mailto: subject field is wrong
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 215046
People
(Reporter: shay_atzitz, Unassigned)
References
()
Details
Attachments
(1 file)
84.71 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: mozilla / firefox
when clicking a mailto: link with a subject in hebrew,
the subject line passed to the mail agent (oulook express in this case),
is wrong
Reproducible: Always
Steps to Reproduce:
1.click the links with the mailto:
2.
3.
Actual Results:
The subject line is wrong
Expected Results:
pass the subject line as is
Reporter | ||
Comment 1•21 years ago
|
||
This screen snapshot shows the message created - with the wrong subject,
and the link that was clicked on the FireFox status line
Comment 2•21 years ago
|
||
*** Bug 242651 has been marked as a duplicate of this bug. ***
Component: Browser-General → General
Product: Browser → Firefox
Version: Trunk → unspecified
Reporter | ||
Comment 3•21 years ago
|
||
This phenomenon also happens with the Mozilla browser, and not limited to the
Firefox Browser.
Comment 4•21 years ago
|
||
The OS field should be changed to All, as this problem is also present under
Linux, and manifests itself whenever the default email client is not from the
mozilla family. I.e. under Linux the Firefox -> KMail combo exhibits this
behaviour as well as under Windows the Firefox -> Outlook/Outlook Express combo.
I believe this has to do with the fact that Firefox/Mozilla will always encode
non-ascii characters in URIs into UTF-8 before passing them on, and above
mentioned email clients cannot handle UTF-8 encoded URIs.
Comment 5•21 years ago
|
||
->BROWSER
(leave it to someone else to set)
Comment 6•20 years ago
|
||
A duplicate of bug 215046?
Comment 7•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 8•20 years ago
|
||
(In reply to comment #6)
> A duplicate of bug 215046?
No
Comment 9•20 years ago
|
||
(In reply to comment #6)
> A duplicate of bug 215046?
Yes it is, and that bug even narrows it down to where we must be going wrong.
*** This bug has been marked as a duplicate of 215046 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•