Quoting URLs leads to HTMLization and subsequent broken links.

[yllus]

See LinuxIdiot's post near the very end of this thread.

When SP33Demon and I tried to quote the post, FuseTalk wrote the URLs out in regular HTML which is then horribly mangled in the post. What's up with that?

 

[Aves]

Without looking I'm just gonna blame it on the WYSIWYG Editor.

 

[PowerMacG5]

Originally posted by: aves2k
Without looking I'm just gonna blame it on the WYSIWYG Editor.

Same here, that's why I stopped using it on my windows computer.

 

[OIKOS]

same here!

 

[yllus]

I'm going to test the WYSIWYG Editor theory.

This is a link to my personal website.

In a few moments, I will quote this post and see what happens!

 

[yllus]

Originally posted by: yllus
I'm going to test the WYSIWYG Editor theory.

<a target=_top class=ftalternatingbarlinklarge href="http://degenerates.org" target=blank>This is a link to my personal website.</A>

In a few moments, I will quote this post and see what happens!

Yeah, looks like you guys nailed the reason.

It makes absolutely no sense though. FuseTalk should take a link - any link - and re-convert it to non-HTML elements when asked to quote a post. How could it possibly know or care that the message was drafted in the WYSIWYG editor?! 😕

 

[Yomicron]

FuseTalk should take a link - any link - and re-convert it to non-HTML elements when asked to quote a post. How could it possibly know or care that the message was drafted in the WYSIWYG editor?! 😕

HTML generated by using the normal posting method:

<a target="new" class="ftalternatingbarlinklarge" href="http://www.google.com">a link</a>

HTML generated by using the WYSIWYG editor:

<a class="ftalternatingbarlinklarge" href="http://www.google.com" target="blank">a link</a>

Notice that they are formatted differently, and have different targets. My guess is that FuseTalk only recognizes the first format as a link, and so the other is considered to just be plain text. IIRC, the WYSIWYG editor is provided by a third-party, which could explain why FuseTalk doesn't recognize the HTML generated by it as a link.

 

[Barnaby W. Füi]

I use privoxy to filter out <a target=....> so I can't see the difference in targets on those, but I've noticed before that fusetalk uses target=new, whereas the HTML standard specifies that to open a new window, you use target=_blank. However, so many people misused it in the early days that browsers have always just opened a new window for any unrecognized target (i.e., no frame with that name), thus exacerbating the problem to the point where even big software commercial packages such as fusetalk misuse the target attribute.

Why is it that whenever I get in a conversation about html, I always end up feeling disgusted? 🙂