2

My styling on this particular SE site is pretty bugged, is this a deliberate QA joke or an actual bug?

Surely this has been asked (if its not a bug) but I couldn't find it.

enter image description here

14
  • Browser information?
    – corsiKa Mod
    Feb 11, 2015 at 16:37
  • @corsiKa latest chrome(40.0.2214.111 m), have tried with adblock on and off. All other SE sites including betas look fine, no zoom, no JS errors
    – undefined
    Feb 11, 2015 at 19:02
  • I am using Version 40.0.2214.111 (64-bit) and it works perfectly for me. (I don't know what the "m" at the end of the version number signifies.)
    – user246
    Feb 13, 2015 at 20:32
  • Interesting, I still have the issue. I'm not too sure what the m means either but I wouldn't imagine it would be an issue of chrome versions
    – undefined
    Feb 15, 2015 at 4:39
  • Although my content is centered, the menu is also to low compared to pm.se for example. I am using chrome Version 40.0.2214.111 m
    – Niels van Reijmersdal
    Feb 17, 2015 at 8:15
  • 1
    Do you happen to be zoomed in/out? (Ctrl + 0 to reset)
    – Oded
    Feb 19, 2015 at 13:35
  • @oded 'All other SE sites including betas look fine, no zoom, no JS errors' nah no zoom or any of the other obvious things like caching, or chrome plugins (incognito is exactly the same)
    – undefined
    Feb 19, 2015 at 18:53
  • 1
    @oded I had a bit more of a play, the content offset left only occurs at browser widths greater than 2145px. The missplaced header occurs for me at all browser widths
    – undefined
    Mar 3, 2015 at 19:57
  • Thanks for hunting that down. I will look into this with our designers.
    – Oded
    Mar 3, 2015 at 20:05
  • @oded np, it only happens on this site, so is probably in the SQA stylesheet
    – undefined
    Mar 3, 2015 at 20:18
  • @oded also the header displacement occurs because #hlogo is 417px and #hmenu is 564px (total 981px) inside a 980px wide container, one of those elements needs to shrink by 1px (im guessing #hlogo a should be 416px. Interestingly applying that change fixes both issues
    – undefined
    Mar 3, 2015 at 20:25
  • It is one of the longest site names/logos we have, which might be the reason. I was under the impression this was fixed earlier, but I guess not completely.
    – Oded
    Mar 3, 2015 at 20:34
  • @Pacerier - looks fixed to me. What browser/OS are you on? Are you zoomed in/out?
    – Oded
    May 12, 2015 at 14:07
  • @Pacerier looks fine on my machine now, and the underlying issue definitely looks fixed if you are still getting an issue it may be a different one.
    – undefined
    May 12, 2015 at 20:59

1 Answer 1

Reset to default
-1

Considering that multiple answers exist in the comment section and considering that the experience seems to be rather limited to your humble self, I'd advice to close this question. Any objections?

Cheers!

3
  • Yes I do object to closing it. Just because you cant see the issue doesn't mean it isn't there
    – undefined
    Mar 3, 2015 at 19:55
  • It's not just me, who can't see it mate.
    – Hannibal
    Mar 4, 2015 at 6:30
  • I have the same problem :)
    – Niels van Reijmersdal
    Mar 4, 2015 at 16:37

You must log in to answer this question.

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