Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

There appears to be some malformed HTML in Meta's sidebar that's causing the chat advertisements to be displayed incorrectly. The module which contains the "Frequently Asked" question list has a "linked" container inside of it, and either it or its parent module element appear to be missing a closing </div> tag.

This results in the subsequent modules (including the chat module) being what I believe to be unintentionally nested. As a result, the chat ads are shifted eight or so pixels to the right, causing part of them to be cut off. Note that this only happens on the main page, where the FAQ links are displayed.

The stripped-down version of the HTML looks like this:

<div class="module" id="interesting-tags">
  <!-- Some very interesting tags -->

<div class="module">
  <h4>Frequently Asked</h4>
  <div class="linked">
  <!-- Some FAQuous links.. -->

  <!-- There should be another closing tag here -->

  <div class="module" id="chat-feature">
  <!-- Some chatty stuff... -->

I've opted to illustrate this tragedy with the following series of panels that compare MSO's sidebar to that of Gaming (complete with FHC and RCE (rchern-compatible emoticons)). The two right-most panels illustrate the shift which results from the nesting:

Verified Genuine Situation-Specific Problem-Solving Thought Process Diagram™

share|improve this question
If it wasn't clear enough, the chat ad in MSO's home page can be reached like this: div#sidebar div.module div.module#cheat-feature -- the FAQ module only ends right before the feed link and the other modules are wrapped into it, resulting in excess padding. – badp Dec 9 '10 at 11:17
up vote 2 down vote accepted

Maybe I should have read your post before fixing this – that would have spared me from having to find the problem myself :)

Will be fixed next time we deploy, thanks!

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .