Website loads halfway down the front page

[Rich Thomas]

Any ideas on how to track the issue down? Works fine on IE and FF..but on chrome it jumps to halfway down the page on loading.

www.vermontindustries.com

[picaflor-azul]

Any ideas on how to track the issue down? Works fine on IE and FF..but on chrome it jumps to halfway down the page on loading.

www.vermontindustries.com

I just spent time trouble shooting this for a client. It must be something that has changed in the new version of chrome. I narrowed the problem down to the manufacturers sidebox. When you turn off the box the problem is fixed, but I have no idea why the browser is having a problem with this particular sidebox.

Thanks,

Anne

[DrByte]

Any ideas on how to track the issue down? Works fine on IE and FF..but on chrome it jumps to halfway down the page on loading.

www.vermontindustries.com

If you temporarily switch your store to use the Classic template, does the problem continue? Of course, switch it back to your current template once you've tested it in a few browsers.
If the symptoms don't occur on all templates, then it could be related to your custom template's CSS or javascript, including things done to it specifically for mobile.

[picaflor-azul]

If you temporarily switch your store to use the Classic template, does the problem continue? Of course, switch it back to your current template once you've tested it in a few browsers.
If the symptoms don't occur on all templates, then it could be related to your custom template's CSS or javascript, including things done to it specifically for mobile.

I can confirm that the problem is present in the classic template. The particular site that I was working on was not a responsive design.
And it also happens when clicking through to other pages.

Here is an example 1.5.3 with the classic template:

http://weblyweb.com/fresh/

I am seeing the problem in chrome Version 38.0.2125.104 (64-bit)

Thanks,

Anne

[RodG]

I can confirm that the problem is present in the classic template. The particular site that I was working on was not a responsive design.

Here is an example 1.5.3 with the classic template:

http://weblyweb.com/fresh/

I am seeing the problem in chrome Version 38.0.2125.104 (64-bit)

Thanks,

Anne

Just to keep things interesting, I'm using chrome
Version 38.0.2125.104 (64-bit)

but I'm NOT seeing any problem with this site (or the vermontindustries site).

Possibly its related to a chrome plugin/extension rather than chrome itself?

Cheers
RodG

[Ajeh]

I am ... I will have to play later with various servers and see if there are differences ...

[DrByte]

Just to keep things interesting, I'm using chrome
Version 38.0.2125.104 (64-bit)

but I'm NOT seeing any problem with this site (or the vermontindustries site).

Possibly its related to a chrome plugin/extension rather than chrome itself?

Cheers
RodG

I tried, using the same version, and I did see it initially on the vermont site, and then after a few refreshes it no longer jumped. Then I opened it again in another tab, and it happened again there.

[RodG]

I tried, using the same version, and I did see it initially on the vermont site, and then after a few refreshes it no longer jumped. Then I opened it again in another tab, and it happened again there.

Alas, I still can't replicate the issue. If I were to take a wild guess I'd say this looks/sounds like a caching issue?

Regardless what the cause, this is probably going to be a pig to debug.

Cheers
RodG

[Rich Thomas]

I just spent time trouble shooting this for a client. It must be something that has changed in the new version of chrome. I narrowed the problem down to the manufacturers sidebox. When you turn off the box the problem is fixed, but I have no idea why the browser is having a problem with this particular sidebox.

Thanks,

Anne

I turned the manufacturer sidebox off and it works great. Ty Ty Ty!!!

[DrByte]

It seems to be that Chrome (and Opera) is repositioning the bottom of the viewport (visible area in the browser) to the top of the first form on the page that contains a SELECT field which has a pre-"selected" entry set in it.
Open bug discussion on Chrome at: https://code.google.com/p/chromium/i...tail?id=423155
Chime in there to let them know you are also affected .. the more the merrier, and the sooner they'll fix it.

The *temporary* workaround until the browsers are fixed is to turn off any sideboxes that display a pulldown which contains a "default" option in it.
Or for the advanced coder, you could disable the code that sets the selected attribute in the corresponding option tag in the html.