This is a migrated thread and some comments may be shown as answers.

[Solved] Unacceptable Level of Formatting Issues in Firefox

13 Answers 341 Views

Editor

This is a migrated thread and some comments may be shown as answers.

Vaughan Reed asked on 11 Mar 2009, 11:08 PM

We are experiencing a high number of formatting and behavourial issues in Firefox for the Telerik Editor, which means our clients can nolonger use Firefox within our CMS system. A support ticket for this was logged months ago but Teleriks response was "The issue is logged in our bug tracking system and todo list with medium priority"

I would be interested to hear what other telerik customers have to say about this issue and how much impact this is having on their application?

The issues we are experiencing are as follows:

RadEditor issues in firefox:

Our Current version of the RadEditor is 7.3.4.0
These issue were reproduced on Firefox 3.0.7

The editor has NewLineBr set to false.

Issue one:

Step 1: Type "Line Number One" and then press enter.
Step 2: Type "Line Number Two"
Step 3. click the "<>" HTML button. The following html is displayed:

Line number one
<p>Line number two</p>
<br />

I would have expected the html to display:

<p>Line number one</p>
<p>Line number two</p>

Issue two:

Step 4: Switch back to Design mode
Step 5: Select all the text and press the delete key
Step 6. click the "<>" HTML button. The following html is displayed:

<br />

Why is the <br /> tag still there?

Issue three:

Step 7: Clear all the text in the HTML editor and switch back to Design Mode.
Step 8: Type "Heading One".
Step 9: Tripple click "Heading One" and apply the H1 style to it.
Step 10: Put the cursor at the end of the "Heading One" line and press enter.

The type is still H1 I would expect it to create a new normal text paragrah after the "H1" line.

Step 11: Type "Heading Two"
Step 12: Tripple Click "Heading Two" and apply the H2 style to it.
Step 13. click the "<>" HTML button. The following html is displayed:

<h1>Heading One
<p>
<h2>Heading Two</h2>
</p>
</h1>
<br />

I would have expected:

<h1>Heading One</h1>
<h2>Heading Two</h2>

Step 14: Switch back to Design mode

The design looks different.

Step 15. click the "<>" HTML button. The following html is displayed:

<h1>Heading One
<p>
</p>
</h1>
<h2>Heading Two</h2>
<p></p>
<br />

What the? How has the html just by switching views. This is closer to what I would expect afterstep 13, but whats with the additional p and br tags?

Issue Four:

Step 16. Clear all the text in the HTML editor and switch back to Design Mode.
Step 17: Type "Line Number One" and then press enter.
Step 18: Type "Line Number Two" and then press enter.
Step 19: Type "Line Number Three" and then press enter.
Step 20: Insert the cursor directly before the "Two" in "Line Number Two" and press enter.

Instead of splitting the line into two paragraphs and setting the cursor before the "Two", the paragraph is split in half and a paragraph is created in between them.

Step 21. click the "<>" HTML button. The following html is displayed:

Line Number One
<p>
<p>Line Number </p>
<p> </p>
<p>Two</p>
Line Number Three</p>

I would have expected:

<p>Line Number One</p>
<p>Line Number </p>
<p>Two</p>
<p>Line Number Three</p>

Issue Five:

I pasted from a word document using the Paste Plain Text. Every paragraph contained double br tags instead of being wrapped in a p tag. This happens despite NewLineBr being set to false.

13 Answers, 1 is accepted

answered on 16 Mar 2009, 02:59 PM

Hi Vaughan,

Up to the issues:

the first issue is not yet fixed because the NewLineBr="false" functionality is our custom implementation and due to the browser problems it is not easy to be enhanced. The default Firefox behavior is to insert <br /> tags instead of wrapping the text in <p></p> tags.
I was not able to reproduce the second issue neither with RadEditor Classic nor with RadEditor for ASP.NET AJAX. You can see the attached video here for more information.
For the third issue, our suggestion is to test the new enhanced FormatBlock tool of the Q1 2009 version of RadEditor. Here is an example: Paragraph Styles.
This is a limitation of the NewLineBr="false" command - the problem is logged in our bug tracking system.
The content pasted from Word is not modified by RadEditor and it is pasted as it is pasted by MS Word. The editor just strips the tags except the <br /> tags but it does not replace the <br> tags with <p> tags. This problem has nothing to do with the editor.

Greetings,
Rumen
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

answered on 16 Mar 2009, 03:52 PM

Rumen,

We are also facing issue two. I am not sure what setting you have that prevents this from happening:

Issue two:

Step 4: Switch back to Design mode
Step 5: Select all the text and press the delete key
Step 6. click the "<>" HTML button. The following html is displayed:

<br />

Why is the <br /> tag still there?

This is how we are using the Radeditor (version 2008_3_1314):

<telerik:radeditor

ID="RadEditor1"

runat="server"

EditModes="Design,Html"

AutoResizeHeight="true"

EnableViewState="true"

BorderWidth="1"

Skin="Telerik"

ToolsFile="../RadControls/Editor/ToolsFile.xml"

EnableResize="false"

ContentFilters="ConvertToXhtml, IndentHTMLContent, MakeUrlsAbsolute, RemoveScripts"

StripFormattingOnPaste="NoneSupressCleanMessage">

<telerik:EditorContextMenu TagName="TD" Enabled="false" />

<telerik:EditorContextMenu TagName="IMG" Enabled="false" />

<telerik:EditorContextMenu TagName="TABLE" Enabled="false" />

<telerik:EditorContextMenu TagName="A" Enabled="false" />

</ContextMenus>

</telerik:radeditor>

Thanks, Lakshman

answered on 20 Mar 2009, 09:50 AM

Hi Vaughan,

Let me emphasise that RadEditor works in Firefox, but only the NewLineBr="false" mechanism should be enhanced. Firefox inserts by default a <br/> tag on enter key press. The default InsertParagraph execCommand of Firefox is almost unusable because it just wraps the current line in <p>content</p> tags and cannot be used for inserting new lines with paragraph tags.
That is why we decided to enhance the NewLineBr property to work in Firefox and provided the ability to insert <p> tags on enter key press when NewLineBr="false". Unfortunately, due to the browser bugs and specific problems it was hard to workaround all appearing side effects and they were logged for fixing in our bug tracking system.

We do appreciate all requests about the improvement of the NewLineBr="false" feature in Firefox and especially the scenario described in Issue 1 and we decided to raise the priority of this problem to high. We will try to fix the problem soon for the SP1 release, but if the time does not permit we will do our best to fix it for the SP2 of the Q1 2009 release.

I would like also to invite you to test the enhanced FormatBlock tool of RadEditor for ASP.NET AJAX Q1 2009 version that is very flexible for configuration and could be used for paragraph insertion.

Until we fix the NewLineBr="false" problem, our suggestion is to set the NewLineBr property to true and use the default browser mechanism for <br/> tag insertion on enter key press.

Best regards,
Rumen
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

answered on 15 Apr 2009, 06:35 AM

Hi Rumen,

We're having the same problem with issue 3. Where if you choose say Heading 1. Then enter some text on one line, and press return and enter some more text on the line below.

Then if we were to try and write some text in between the 2 headings, and set it to normal, it will never work as the heading tag wraps the whole area. This happens in firefox.

Can you suggest any work around to use? Obviously we are unable to upgrade to RadEditor for ASP.NET AJAX Q1 2009 to use FormatBlock tool, as we are running Q1 of 2008 and it would mean we'll have to pay to upgrade.

answered on 15 Apr 2009, 07:52 AM

Hi Quangster,

Could you please make sure that the NewLineBr property is set to true in your RadEditor Classic declaration and try to reproduce the problem again?

The RemoveFormat command that the editor fires when the user chooses the Normal item in the FormatBlock dropdown is a browser implementation, and it does not remove the formatting from selection. To remove the formatting the user should select the whole passage, but this command does not handle all scenarios.

Please, also note that the development of RadEditor Classic was stopped in favor of the new and much enhanced RadEditor for ASP.NET AJAX. We do not plan for the time being to create a custom implementation for the RemoveFormat command in both RadEditor Classic and RadEditor for ASP.NET AJAX.

Sincerely,
Rumen
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

answered on 05 May 2009, 02:15 AM

Hi Rumen,

Like Vaughan has suggested, we cannot set NewLineBr to "true", as our clients format their content in paragraphs.

Obviously these are bugs, so how are we supposed to fix it without being force into an upgrade/renewal?

Further more our clients are running into more issues regarding formatting issues, see scenarios below.

Issue #	Browsers Affected	Description	Replication Steps
1	Firefox, IE	Cannot change text in between paragraphs paragraph between two headings from "Heading" back to "Normal" font.	1. Open editor. 2. Change format to say "Heading 1". 3. Type in a heading "Test 1", then press enter, then type in "Test 2". 4. Now go to the end of "Test 1" then press enter to create a paragraph between the two headings. 5. Attempt to change the style back to "Normal". This does not work!
2	Firefox and IE on (Release Q1 2008)	When creating bullet points, when clicking indent, only the bullet points styling changes, no indents occur.	1. Click bullet list option. 2. Type in a few points. 3. Select the points and click indent. 4. Notice only the bullet point symbol changes although no indents occur. Only when you switch from design view to html view and back does it fix up the indenting.
3	IE	Inconsistent paragraph tags.	1. Open editor. 2. In "Normal Style" Type in "First line.", Press Enter. 3. Type in "Second line". 4. Highlight "Second line" and change to "Heading 1", press enter. 5. This should go back to "Normal" then type in "Third line". 6. If you switch to html view the html looks like this "First line <h1>Second line</h1> <p>Third line</p>" Enter should be consistent to create paragraphs no matter which text style you're in.
4	IE	When changing text in paragraphs back to "Normal" it grabs the containing div's class attribute and creates them in each of the paragraph tags.	1. Open Editor 2. Go to html view. 3. Paste in following html. <div class="customstyle"> <p>This is the first line.</p> <p><h1>This is the first heading</h1></p> <p>This is the last line.</p></div> 4. Go to design view. 5. Select "This is the first heading" and change the style back to "Normal". 6. Go to html view. Below is the result html. <p class="customstyle">This is the first line.</p><p class="customstyle"> </p><p class="customstyle">This is the first heading</p><p class="customstyle"> </p><p class="customstyle">This is the last line.</p> Here you can see the container div is completely removed! And each paragraph tag has class="customstyle" added. This ruins our formatting dramatically, most of the time causing the whole page to lose it's styling.

Regards
Quang

answered on 07 May 2009, 03:37 PM

Hello Quangster,

The four problems reported, if we understand them correctly, of course - are not related directly to NewLineBr property.

NewLineBr property has different behavior in IE and FireFox.
In IE, by default, when pressing Enter, the browser will create/wrap content in P tag. In FF, the browser will insert a BR. Speaking from a historical perspective, the huge majority of users expect the FireFox behavior, and want it as the default one. Hence, for years, this has been the default behavior of RadEditor. To achieve it, the editor features (in IE) a custom implementation which prevents P's from being inserted, and instead inserts a BR.

While implementing the (non-default browser behavior) has been relatively easy for IE, implementing the ability to insert P tags in FF is a much harder task. While such functionality was eventually implemented in RadEditor, it does not cover all possible scenarios and can certainly be improved. This is in our plans for the Q2 2009 release. And yes, if you wish to take advantage of it, you will need to upgrade to this version - once that it is out.

Now, back to your four reported problems. Since the wording is a bit scarce, and the problems are mixed (IE + FF), it is not possible to claim for sure what is fixed, and what is an editor bug or the behavior of the browser. However, since two of the problems are related to the FormatBlock tool, I wish to point out that this tool underwent a major enhancement in the Q1 2009 (for all supported browsers). My suggestion is to test it using the following example:
http://demos.telerik.com/aspnet-ajax/editor/examples/formatblock/defaultcs.aspx

A number of enhancements to this functionality have been made, and the currently available Internal Build version of Telerik RadControls behaves even better than the one used in the online demos. So, regarding question #1 and #4, my suggestion is to give this a try.

Regarding issue #2 - from the description it seems like the default (expected) browser behavior. Whether this is the case, you can test with other available web-based WYSIWYG editors and compare the results.

Regarding issue #3 - "Inconsistent paragraph tags in IE" - I am not sure what this is supposed to mean. If I understood correctly, you have set in the editor NewLineBr = "true". What this setting does is turn off the editor's handling of the Enter key, and turn on the browser's mechanism which inserts P tags. As far as P tags are concerned, the IE behavior in this case is just as it is supposed to be - that is, indentical to MS Word. Hence, from the information provided it is unclear what the issue is.

In all cases, if you believe that there is an issue outstanding with the editor, my suggestion is to provide steps to reproduce - as well as "expected" result and "actual" result. This will allow us to answer in a more precise manner.

Best regards,
Tervel
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.