alfonsoml wrote:Send a bug report to Microsoft, they are the ones that automatically do that conversion.
Adding child nodes and setting inner HTML doesn't trigger this conversion, so it must be some other IE functionality FCKeditor is using. Can you elaborate on where and how this happens? Thanks
alfonsoml wrote:when you type a url, IE detects that and say: "hey, that's an URL, let's make a link". And that's all, no way to alter it that I've ever read of.
Can you try again, this time in technical terms? That is if you know what's going on.
I don't understand what you are asking for. Have you tried to type an url in IE with FCKeditor? that conversion happens automatically, I don't know how to explain it better, but it's something internal and you can't get much further than that.
Does some plugin exist for IE that solves this? In my application, the editor few persons use it very and it would be relatively easy to solve it if a plugin exists.
alfonsoml wrote:I don't understand what you are asking for. Have you tried to type an url in IE with FCKeditor? that conversion happens automatically, I don't know how to explain it better, but it's something internal and you can't get much further than that.
It's like an explanation of how an internal combustion engine works would be to turn the ignition key.
What I'm looking for is the technical reason IE behaves this way. Something along the lines of "Because Microsoft doesn't support the standard DocumentRange interface, we are using Microsoft's non-standard TextRange objects to manipulate text in IE and when one of those ranges is selected, IE automatically inserts an anchor if [...fill in the blank...]".
It also makes no sense to tell people to report this as a bug in IE, since this is Microsoft-specific functionality and they can implement it any way they like.
alfonsoml wrote:I don't understand what you are asking for. Have you tried to type an url in IE with FCKeditor? that conversion happens automatically, I don't know how to explain it better, but it's something internal and you can't get much further than that.
It's like an explanation of how an internal combustion engine works would be to turn the ignition key.
What I'm looking for is the technical reason IE behaves this way. Something along the lines of "Because Microsoft doesn't support the standard DocumentRange interface, we are using Microsoft's non-standard TextRange objects to manipulate text in IE and when one of those ranges is selected, IE automatically inserts an anchor if [...fill in the blank...]".
The conversion is done automatically by the IE engine, so it's MS the one that should provide an event or some execCommand to disable that functionality in a reasonable way.
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
Andre
Re: Disable autoconversion text in URL
Have you tried to type an url in IE with FCKeditor? that conversion happens automatically, I don't know how to explain it better, but it's something internal and you can't get much further than that.
Re: Disable autoconversion text in URL
In my application, the editor few persons use it very and it would be relatively easy to solve it if a plugin exists.
Re: Disable autoconversion text in URL
What I'm looking for is the technical reason IE behaves this way. Something along the lines of "Because Microsoft doesn't support the standard DocumentRange interface, we are using Microsoft's non-standard TextRange objects to manipulate text in IE and when one of those ranges is selected, IE automatically inserts an anchor if [...fill in the blank...]".
It also makes no sense to tell people to report this as a bug in IE, since this is Microsoft-specific functionality and they can implement it any way they like.
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
Re: Disable autoconversion text in URL
And you are missing the facts.
The conversion is done automatically by the IE engine, so it's MS the one that should provide an event or some execCommand to disable that functionality in a reasonable way.