Page layout disrupted when a break tag interrupts a div within a post [#105523]

When I publish a node (type = blog) as "Promoted to front page" and "Sticky at top of lists," the page layout on the home page breaks, with the right sidebar dropping below all content and moving to the left side.

If I assign the same node, without changing the publishing options, to be the "Default front page" on the "Site information" admin page, the front page does not break.

If I assign the node to "Sticky at top of lists" but do not promote to front page, the /blog page displays normally, without breaking.

I have gone as far as I can in troubleshooting, fiddling with style.css, but to no avail. The block shows up in the Firefox Developer toolbar as class = node sticky, but I'm not seeing a correspondence between what's in the style.css and what's showing up on the screen. I'm afraid I'm not skilled enough to contribute much more insight than this.

Comments

Comment #1

RobRoy commented 28 December 2006 at 01:37

Status:

Active

» Postponed (maintainer needs more info)

A screenshot and browser information would help as well.

Comment #2

joeshirley commented 28 December 2006 at 01:37

Status:

Postponed (maintainer needs more info)

» Active

More info: I've just solved the immediate problem: a had found its way inside a

on the post causing the problem. Moving the outside the

makes the page display properly.

I'm not sure where this question goes, then:

Is there a way for Drupal to patch broken divs before rendering the page? When users can insert a anywhere, it invites trouble. Are there other tags that would cause similar problems?

Comment #3

joeshirley commented 28 December 2006 at 01:41

Sorry, didn't add the code tags:

a <break>had found its way inside a <div> on the post causing the problem. Moving the <break> outside the <div> makes the page display properly.

The question: Is there a way for Drupal to patch broken divs before rendering the page? When users can insert a <break> anywhere, it invites trouble. Are there other tags that would cause similar problems?

(I'm using Firefox 2 and IE7.)