Closed
Bug 3193
Opened 26 years ago
Closed 26 years ago
[PP] page with <br clear=all> before </center> shows blank
Categories
(Core :: DOM: HTML Parser, defect, P2)
Tracking
()
VERIFIED
FIXED
People
(Reporter: akkzilla, Assigned: rickg)
References
()
Details
The URL given contains a <center> tag, a heading, then a <br clear=all> (because
there were some aligned images there in the original, omitted for brevity) and
never closes the center. This confuses the layout engine, or maybe the parser,
to the point that nothing on the page is rendered at all.
4.5 shows the page fine. It doesn't continue the centering past the br. I'm
not sure whether the centering should be extended past the br or not, but a
completely blank page (can't even see the heading) certainly isn't the right
response.
This happens on the 2/18 and 2/19 Linux trees, but does NOT happen on a Windows
2/18 build.
Updated•26 years ago
|
Whiteboard: Clarification requested regarding BR CLEAR=ALL behavior
Comment 3•26 years ago
|
||
I need clarification on this bug before I verify it as fixed. Using the 3/9
build, the page renders in its entirety (which was part of the problem).
As I understand it, the BR Clear=ALL starts a new line below the line where left
and right margins are cleared of floating objects (typically images or tables).
Although it does not conform to the definition above, does BR CLEAR=ALL have any
effect on (does it 'break')the CENTER element tag? If it does not, then the page
renders correctly, centering the second sentence. If BR CLEAR=ALL 'breaks'
CENTER behavior, then the page does not render correctly.
Note: the test case has a superfluous ending ANCHOR element tag which, whether
included or not, does not change behavior.
Updated•26 years ago
|
Whiteboard: Clarification requested regarding BR CLEAR=ALL behavior → Pending clarification requested 3/9 regarding BR CLEAR=ALL behavior
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Whiteboard: Pending clarification requested 3/9 regarding BR CLEAR=ALL behavior
You need to log in
before you can comment on or make changes to this bug.
Description
•