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...]".
Let's see if you can understand it this way: copy this html and create a new html with just this content, nothing else
<p contentEditable="true">finish this url and press space: http://www.google.c </p>
Now open that html file in IE. You see, there's no <head>, no <body>, no scripts, no event-handling, no styles, no doctype, look carefully at the source code. Now follow the instructions in the file, examine everything and tell me what kind of explanation you can give about that behavior.
A.M. wrote: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.
Precisely, they are the ones that have implemented it, and if you don't like something about it, it doesn't make sense to ask other people to fix those problems. Someone thought "when someone is typing an url it will be useful to automatically turn that text into a link", and they were mostly right, except that they forgot about the "but sometimes they might not want that conversion, so we must provide a way to avoid it in those situations". If you don't remind MS about the problems in their programs they won't have any reason at all to fix them.
Do you want another example?: show us how do you disable the Safari spellchecker in some field in a web page. You know that you can set spellcheck="false" in Firefox, but, How do you avoid the red underlines in Safari while you are writing some text? Who do you think that should change some code?
alfonsoml wrote:Let's see if you can understand it this way: copy this html and create a new html with just this content, nothing else
<p contentEditable="true">finish this url and press space: http://www.google.c </p>
See, that was easy - this is the technical reason you could just say this from the start.
alfonsoml wrote:
A.M. wrote: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.
Precisely, they are the ones that have implemented it, and if you don't like something about it, it doesn't make sense to ask other people to fix those problems.
You are missing the point here. You are using Microsoft-specific functionality that is designed to do what it does. More specifically, adding ContentEditable to <body> turns IE into an HTML editor and FCKeditor just happens to use this functionality, which makes this side effect your problem because you made a design decision to use this IE feature as the underlying editing mechanism and the resulting HTML is not what is expected or documented.
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
Let's see if you can understand it this way:
copy this html and create a new html with just this content, nothing else
Now open that html file in IE.
You see, there's no <head>, no <body>, no scripts, no event-handling, no styles, no doctype, look carefully at the source code.
Now follow the instructions in the file, examine everything and tell me what kind of explanation you can give about that behavior.
Precisely, they are the ones that have implemented it, and if you don't like something about it, it doesn't make sense to ask other people to fix those problems.
Someone thought "when someone is typing an url it will be useful to automatically turn that text into a link", and they were mostly right, except that they forgot about the "but sometimes they might not want that conversion, so we must provide a way to avoid it in those situations".
If you don't remind MS about the problems in their programs they won't have any reason at all to fix them.
Do you want another example?: show us how do you disable the Safari spellchecker in some field in a web page. You know that you can set spellcheck="false" in Firefox, but, How do you avoid the red underlines in Safari while you are writing some text? Who do you think that should change some code?
Re: Disable autoconversion text in URL
See, that was easy - this is the technical reason you could just say this from the start.
You are missing the point here. You are using Microsoft-specific functionality that is designed to do what it does. More specifically, adding ContentEditable to <body> turns IE into an HTML editor and FCKeditor just happens to use this functionality, which makes this side effect your problem because you made a design decision to use this IE feature as the underlying editing mechanism and the resulting HTML is not what is expected or documented.
Andre
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.