Open Bug 369502 Opened 17 years ago Updated 3 years ago

Firefox and tidy add line breaks within code blocks

Categories

(Core :: DOM: Editor, defect, P5)

1.8 Branch
x86
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: deesto, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1

The combination of Firefox 2.0.0.1, Plone 2.5.1, and mxTidy causes undesired line breaks to appear in code blocks when a page is edited and saved.

Reproducible: Always

Steps to Reproduce:
1. Open an HTML page for editing that contains <pre /> tags (or create a new one).
2. Save the page (even if no changes are made).

Actual Results:  
The browser adds a <br /> tag after each line of code within a <pre /> tag. If <br /> tags already exist from previous edit sessions, these tags are multiplied.

Expected Results:  
Additional <br /> tags should not be rendered within code, which is expected to be presented literally as-is (i.e, no additional tags or elements added during rendering).

Example: While editing a page in Plone, a user creates a code block using a <pre /> tag, containing a single line ("<pre>text</pre>"). The user saves their changes, the code is run through tidy, and Firefox seems to interpret "<pre>text</pre>" as "<pre>text<br /></pre>". The saved page appears with an extra <br /> at the end of the code line.  As the page is edited again, the <br /> tag is multiplied by two, and so on.

System information:
Firefox 2.0.0.1, RHEL4
Server information:
Plone 2.5.1, CMF-1.6.2, Zope (Zope 2.9.5-final, python 2.4.3, linux2), Five 1.3.7, Python 2.4.3 (#1, Jan 9 2007, 12:05:24) [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)], PIL 1.1.5
tidy installation information: egenix-mx-base-2.0.6, egenix-mx-experimental-0.9.0
I've tested code on every platform I could get my hands on, and only Mozilla-based browsers (both Firefox and Seamonkey, on both Linux and WinXP) reproduce this behavior.

Folks at Plone confirm that they are utilizing only Firefox's standard Midas editing component.
Version: unspecified → 2.0 Branch
Component: View Source → Editor
Product: Firefox → Core
QA Contact: view.source
Version: 2.0 Branch → 1.8 Branch
QA Contact: editor
Any updates on this?  Is this fixed in Firefox 3?

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.