Msg#: 4232292 posted 9:28 am on Nov 19, 2010 (gmt 0)
Just tonight a strange problem has developed on a new template I'm using on my sites. Keep in mind before beginning, that I've been using this template for two+ months daily without issues at all.
Despite that, tonight I noticed that all pages that use this template are shifting vertically upward after the page completes loading - completely removing the default browser margin/padding between the top of the web page and the bottom of the browser window.
For this template, I didn't define a top padding or margin for the "body" tag in CSS (I havent' done it on several other templates either - templates which are performing just fine, btw).
Trying to describe this, here is what happens in order:
1. Page Begins to Load 2. The default padding between bottom of the browser window and the top of the web page appears. 3. Page Continues to Load 4. Page finishes loading and at the same time the default padding between the top of the web page and the bottom of the browser window simply collapses - pushing the top of the web page up directly beneath the browser window, causing the page to "suddenly shift vertically".
Anyways, since I've been using this template for 2+ months without any problem in all browsers, I'm totally confused at why all of a sudden (in both IE and Firefox) this problem started to happen tonight on this one template.
I've tried to fix this problem by adding padding to the Body tag. And this is a partial but even a more annoying fix. The page still jumps with this fix. However, the page doesn't jump all the way to the top but retains the padding set in the body tag.
Any advice on what might be wrong? And how to fix it?
Msg#: 4232292 posted 9:40 am on Nov 19, 2010 (gmt 0)
That is spooky jimh009 - I can't imagine how it could be CSS if you hadn't made any changes and the rest of it is still sweet.
The only other thing I can think would be that your site has been hacked and this is a side effect of that.
Msg#: 4232292 posted 9:50 am on Nov 19, 2010 (gmt 0)
Yeah, it "was" a spooky thing. Thankfully, it's past tense now.
Must be something on Amazon's end, apparently. Hopefully they get it fixed soon or this script is gonna be yanked!