Closed Bug 20083 Opened 26 years ago Closed 26 years ago

[TEXT] Line breaks aren't handled properly after start tags and before end tags.

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

VERIFIED DUPLICATE of bug 2750

People

(Reporter: jonblake, Assigned: erik)

Details

Attachments

(1 file)

From the notes on line breaks in the HTML 4.0 spec: SGML (see [ISO8879], section 7.6.1) specifies that a line break immediately following a start tag must be ignored, as must a line break immediately before an end tag. This applies to all HTML elements without exception. http://www.w3.org/TR/REC-html40/appendix/notes.html#notes-line-breaks Currently, the line breaks are being contracted into a single space whereas they should be ignored completely. Testcase: <html> <head><title>Line Break Test</title></head> <body> <p>There should be no spaces between the &quot;|&quot;s on both of the following lines (both lines should be exactly the same):</p> <p><tt>|</tt><tt>|</tt><tt>|</tt></p> <p><tt>|</tt><tt> | </tt><tt>|</tt></p> </body> </html>
Assignee: troy → kipp
Updating to default Layout Assignee...kipp no longer with us :-(
Why are you re-reassing layout bugs? Do NOT touch layout bugs. The bugs are assigned to Kipp so they can stay neatly organized until we have a new owner for the block/inline code.
mass moving all Kipp's pre-beta bugs to M15. Nisheeth and I will prioritize these and selectively move high-priority bugs into M13 and M14.
Summary: [testcase] Line breaks aren't handled properly after start tags and before end tags. → [TEXT] Line breaks aren't handled properly after start tags and before end tags.
*** Bug 25822 has been marked as a duplicate of this bug. ***
mine! mine mine mine! all mine! whoo-hoo!
Assignee: kipp → buster
moving all buster m15 bugs to m16.
Target Milestone: M15 → M16
Won't make beta2 if it stays on my list. Moving to M18.
Target Milestone: M16 → M18
Here is the initial batch of layout [TEXT] bugs. I'll search for more today, but this should keep you busy for a while! Please review these for possible dogfood or nsbeta2 candidates, and assign your own priority and milestone for each. The current settings were relative to my bug list, and they might not make sense any more.
Assignee: buster → erik
Confirmed the behavior. Both WinNav4 and WinIE5 behave this way too. Accepting bug, but marking M19.
Status: NEW → ASSIGNED
Target Milestone: M18 → M19
*** This bug has been marked as a duplicate of 2750 ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Verfiying.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: