The relevant code is actually in the html module and it's intent was to make code more portable i.e. to ensure that if a site had 2 aliases(site1.com & site2.com) that the domain was stripped and the path was made absolute as seeing site1.com links on site2.com would feel "wrong".

This was done in the html module as the editor at the time (FCK I believe) did not support an absolute/relative link function, but as telerik now does it could be changed - the only issue being that it would contain provider specific code as telerik stores the info in a different place from ckeditor etc.

The "best" solution would be to make it an attribute on the provider, but I suspect that as telerik is the new standard the easiest/quickest solution would be to simply check for and respect the telerik settings i.e. if using telerik check for it's absolute/relative links setting and apply it, if not telerik apply the existing logic - if someone wants to log this at support.dotnetnuke.com I'll see about getting it fixed in a future release.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Thank You for your feed back on these things guys,

Do you have any feedback as to why I span tab is injected by default when you click on apply style from the apply style dropdown list in the rad editor if you don't first start writing some content and than highlight the content in which you want the style applied to.

Again if you do write content FIRST and than highlight that content and apply style it does put the class on the block selector like the p tag which then takes alignment properties but if you do not highlight content before clicking on apply you do not get a class attribute in the block element p before the content is rendered between the two tags but rather a nested span element with the class attribute and since span is an inline element I suspect this is why certain alignments just don't take when the class is wrapped in a span tag.

Also needing some feedback on the radeditor as it relates to Firefox 7 and prehaps previous versions in regards to span tags being generated weather you type in the content and highlight than apply the style or weather you simply apply a style and write the content. It seems like in firefox only does a class get invoked into a span tag when you click on apply style no matter which way you do it in the rich text editor (the new rad editor or old telerik editor as I have tested this theory in both).

Again things seem to work correctly when typing content and highlighting than applying the style when in chrome in IE as they will than both inject the class attribute within the p tag instead of generating an inline span tag to do this injecting within the p tag but in firefox this is not the case.

My solution or work around at this point in time has been to press the space bar than highlight the space by holding down shift and highlighting the space character and than applying the desired style with alignment properties (for example centering text) Than I can simply start typing and overwrite that space character with content which than shows up as expected with all attributes applied but this certainly could be more of a headache for technically challenged who simply knows how to create some content based on the rich text editor and not digging into the html tags.

Thanks for your help,

Bo

Hello Westa already there on DNN 6.0.2 what would be the best way to approach this issue should I address it on gemini or do you think their is already some awareness out there about these issues in Firefox.

I must say this isn't the first issue I have run up against in regard to how the telerik editor worked in relationship to firefox. Forexample I was doing some stuff with live tooltip a while back which uses inline tokens on href tags in order to invoke tooltips on a particular targeted element or parts of an element.

When I tried to do this through firefox it came out all wrong with http prepending (as was discussed in this thread already) and other things that telerik or firefox tried to do to make it "appear" more like it was a link. IE never messed with the way I typed information in the link area. This was even a problem when I went straight for the source area of the editor and physcially typed it in using html markup instead of rich text editiing.

I don't think issues like these seem to be tuned to just Firefox 7 but earlier versions as well. I am wondering if their is any knowledge in regards to fighting with these kinds of issues in the past and if their was any attempt to address them but didn't follow through do to issues that were run into when trying to make DNN more seamless in regards to its core functions with the two big giants of Firefox and IE.

I don't know why these problems don't seem to surface on chrome at least from what I could see so far but for whatever reason if their is a quirk somewhere with a provider or other function more than not the issue hangs in firefox even if it doesn't in IE.

Of course I know it isn't possible to guarantee that every t is crossed and every i dotted for smooth experience in every browser that someone might happen to have installed but firefox is a big name browser (even though it is becoming less and less of that as chrome is taking so much of the market share now) and I would be interested if you,or Cathal, or Subastian can shed any light into issues DNN team runs into when it comes to Firefox as opposed to IE or even perhaps Chrome as IE and Chrome seem like they run on similiar wave lengths in that more times than not if something works in IE it probably will in chrome as well.

Thanks,

Bo