TL;dr: Ok, there are 3 issues:

  1. The right part of all fields are not aligned correctly. Rev, Title, the editor field and the preview has different widths.
  2. The small yellow ? is being chopped off.
  3. The wdm-container div class has a overflow: hidden rule that is added by one of my Addons. This rule works fine in any of the SE sites but here...

I'm taking a screenshot of the current post editor. As you can see the right side is chopped off. I believe some declared css width is making a mess, but I haven't tested fully. Also,the right margin is off, I believe for the same reason.

**Post question:**                             **Suggested edits:**

enter image description here                                                         

This happens in Firefox (Iceweasel 25.0a2 Debian testing) with and without addons, Greasymonkey, etc.

Chromium seems unaffected:

**Suggested edits:**                            **Ask question:**

enter image description here                                                        enter image description here

But is well known that chrome/ium is broken by default.

  • I think OS / browser version may help here... (I can't emulate this on Win7 + FireFox 23)
    – Drav Sloan
    Commented Sep 16, 2013 at 17:01
  • I can't emulate on Debian Firefox 23.0.1 either. I'm also not 100% sure what the problem is. Could you post the entire screenshot? What is the difference between whatyou see in iceweasel and chrome? Is this about the ? being slightly sliced?
    – terdon Mod
    Commented Sep 16, 2013 at 17:22
  • Mmhh... weird, just now it was working when I changed the theme... seems like a bug between Iceweasel, the theme and the css... Lets see if I can work around.
    – Braiam
    Commented Sep 16, 2013 at 17:29
  • @terdon I think is a bug of Firefox 25, can you replicate there?
    – Braiam
    Commented Sep 16, 2013 at 17:35
  • @Braiam don't really want to upgrade, this is my stable work machine.
    – terdon Mod
    Commented Sep 16, 2013 at 17:38

1 Answer 1


Declining this bug, as it involves a pre-release version of a browser.

We support current releases of browsers, not alpha or beta versions.

You must log in to answer this question.

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