The problem is that <span>s can not be nested - both because you can not have divs in spans and also it is later impossible to find the matching </span> :-(
The reason for those unfortunate <span class="nolink"> and <span class="lang"> was that html editor did not support custom tags, this is not a cane anymore in tinymce of fckeditor.
Description
The problem is that <span>s can not be nested - both because you can not have divs in spans and also it is later impossible to find the matching </span> :-(
The reason for those unfortunate <span class="nolink"> and <span class="lang"> was that html editor did not support custom tags, this is not a cane anymore in tinymce of fckeditor.
Along with this, it would be nice if the filtering system broke up the texts into "linking" and "nolinking" chunks before sending them to the filters, so that the nolink tag always works for all filters.
I guess to be correct for this we need to do either one of these:
1) have all filters declare that they are "linking" type filters or not, so that we just apply to these.
2) change the tag name to "nofilter" and support "nolink" as a undocumented alternative for backward compatibility.
Martin Dougiamas added a comment - 11/Dec/08 01:39 PM Along with this, it would be nice if the filtering system broke up the texts into "linking" and "nolinking" chunks before sending them to the filters, so that the nolink tag always works for all filters.
I guess to be correct for this we need to do either one of these:
1) have all filters declare that they are "linking" type filters or not, so that we just apply to these.
2) change the tag name to "nofilter" and support "nolink" as a undocumented alternative for backward compatibility.
I guess to be correct for this we need to do either one of these:
1) have all filters declare that they are "linking" type filters or not, so that we just apply to these.
2) change the tag name to "nofilter" and support "nolink" as a undocumented alternative for backward compatibility.