GNOME Bugzilla – Bug 645621
[regression] forwarding a URL from firefox-3.x or 4.0 results in mangled URL
Last modified: 2012-08-14 14:15:59 UTC
I'm not sure that this is an evolution problem. When I try to forward a URL in firefox (File->Send Link...) I get the expected compose mail popup in evo. The subjec is correct, but in the message area I see: h ttps://bugzilla.gnome.org/enter_bug.cgi?product=Evolution Clearly there shouldn't be a line break after the h. I'm running the git master of evo and friends, although this has been going on for some time (I actually think that I'd already reported this, but couldn't find the bugzilla entry). I've had this problem since firefox-3.6.x and it is still happening in firefox-4.0
Thanks for a bug report, but this works fine here, both with Firefox 4.0.0 and 3.6.16, the URL is not wrapped. I would expect composer doing that, due to line limits, rather than firefox, though it works as expected even with longer URLs than that yours here, no matter if in HTML or plain text mode. The paragraph mode is Preformatted on a line with the URL when opening the composer, and changing it to Normal doesn't wrap the URL either. Usual line character width for Normal paragraph style is 72 letters. I didn't find GConf key where this can be changed from the outside, it seems to be hard-coded inside the executable. Could you check your Composer settings in Preferences, what paragraph style is set on a line with the URL and whether changing it changes the line wrapping too, please?
I've got none of the composer options set (even the default character set). The reply style is quoted, forward style is attachment, keep signature is set to above the original message.
Hmm, then we have it pretty the same. I've not much idea how this could happen, apart of things mentioned in comment #1, though those are rather thoughts.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 627001 ***