55658 - Tune Send Link

Status: VERIFIED WONTFIX

(MailNews Core :: Composition, defect, P3)

Description

[Ben Bucksch (:BenB)]

Reproduce:
1. Browse in Navigator
2. File|Send Link

Actual result:
HTML composer with body
<example>

http://www.example.com
</example>
Note the empty line. The URL is a link.

Expected result:
HTML composer with body
<example>
<http://www.example.com>
</example>
The URL, including angle brackets, is an URL.
During sending, the askSendFormat dialog must *not* come up.

Same for File|Send Page (but the askSendForamt dialog may come up in this case).

Comment 1

[Ben Bucksch (:BenB)]

Changing personal priorities. Giving away most of my bugs :-( (reassigning to
default owner).

I will still track these bugs closely. If you need my input, feel free to ask me.

New owner: Please do *not* close these bugs (as WONTFIX or whatever you may
find) unless they are fixed. Rather, reassign to <[e-mail]>, if you
don't want to work on them.

Comment 2

[Håkan Waara]

Most often you want to make a comment to the link, or at least write "Hi" before
sending. I think this linefeed is on purpose, it's not a bug - it's a feature! :)

Seriously though, this is a clear wontfix. It would just be more hassle for most
users to press <enter> every time they sent a link to make a comment.

Comment 3

[Ben Bucksch (:BenB)]

The comment is supposed to go *after* the link - the mail is about the webpage,
so the link should be in the first line, i.e. at the very top.

Comment 4

[Ben Bucksch (:BenB)]

BTW: That's the way 4.x works.

Comment 5

[Jean-Francois Ducarroz]

We put an empty line else there is no way to type text before the link whitout
beeing part of it.

When you send the message, as long you don't enter yourself some rich
formatting, the ask me dialog does not come up.

We put the angle brackets only when you are setup to use plain text composition.
The only potential problem I see is that when we translate from HTML to
plaintext during the send operation, we are not putting the link between angle
brackets! If you really think we should do that, plaease file a new bug.

I don't know how to resolve this bug: should be a won't fix, a WFM or invalid!
ANyway, I'll use Won't fix to avoid QA to waste time on it trying to figure what
to do with it...

Comment 6

[Ben Bucksch (:BenB)]

.