Closed Bug 25011 Opened 25 years ago Closed 25 years ago

Support closing brackets in freetext URLs

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: bugzilla, Assigned: BenB)

Details

If you send a text plain mail with the following link (in one line) the line 
gets wrapped after the =ps

http://x21.deja.com/[ST_rn=ps]/getdoc.xp?AN=569255837&search=thread&CONTEXT=
948306399.1876754433&HIT_CONTEXT=948306399.1876754433&HIT_NUM=3&hitn
um=0

using 2000012508
Looks to me like the message is sent correctly (URL is not wrapped), but then on
the reading side, our URL-ification code wraps it.

Maybe we're getting bitten by our desire to Do What I Mean, which sometimes
involves breaking a URL according to common human usage. e.g. "Check out this
URL (http://home.netscape.com)" Should the closing paren be in the URL or not?
Tough call. Anyway, I think BenB owns this issue, so over to him, cc rhp.

Guys, a possible suggestion: if you match the positions of the opening bracket,
you might notice that the URL scheme comes *before* the opening bracket and thus
allow URL-ification to include the characters after the closing bracket. But if
you noticed the URL scheme came *after* the opening bracket, then you could
assume the DWIM case I mentioned above.
Assignee: phil → mozilla
What Phil said.

However, my code does not wrap it. It just closes the a tag after the "=ps" and
the display code must wrap it. Try to make the window really large and the URL
is in one line. Changing Summary.

Phil, your suggestion is a good idea and indeed possible. But personally, I
think, the FindURL code is already fancy enough (>300 lines (!) not including
validity checks). Use angle brackets for such odd URLs (as you should always do
BTW).
WONTFIX.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Summary: long url from deja news wraps into new line → Support closing brackets in freetext URLs
verifying old bugs...
build 2001013020
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.