jonmrich
Member
Posted 11 months ago #
Yesterday (from out of nowhere) a vertical scrollbar started appearing in my posts. (example here: http://www.doseofdigital.com/2011/05/pharma-facebook-commenting-final-story/).
I hadn't changed anything besides writing new posts. I tried deactivating of all my plugins and that didn't work. I updated to 3.2 and that seemed to fix the issue yesterday. However, I look at my site today and the scrollbar is back. I also tried editing my CSS to include overflow: hidden; in the correct places, but that didn't work either.
A couple of observations: the scrollbar only seems to be in Chrome and Safari. FF and IE8/9 don't have it. In both Chrome and Safari, my 404 page doesn't have the scrollbar (for example: http://www.doseofdigital.com/asdfasdfasdfasdf).
Any ideas? I can't see anything in my source code that could be causing this.
Thanks
JMR
Have you used firebug in FF (or whatever the developer tool chrome has built in) to poke around and see if you can determine what css would be causing that?
jonmrich
Member
Posted 11 months ago #
Found the CSS line. Tried adding overflow: hidden and that didn't work. I can change the height of the column to whatever I want and that does affect the size of the box within the column that has the scrollbar. So, technically, I could make it height: 50000px and the scrollbars would be gone, but you'd never get to the bottom of the page though.
I looked at the developer tools in Chrome and see that the height is auto assigned, but I can't tell what the parent is.
jonmrich
Member
Posted 11 months ago #
Adding height: auto; to this one part of the CSS (#left-column) didn't do anything either.
jonmrich
Member
Posted 11 months ago #
Update: this appears to be caused by some javascript. Looked at developer tools and see this error: Refused to set unsafe header "Content-length"
This is happening only in Webkit browsers. Is there a way to figure out the offending script?
Of note: it's fixed now, so I'm guessing that someone is tinkering with their js that I call on the page and fixing and breaking it. Still would like to figure out which one is causing it though.
