|
|
Posted by Mika on 11/23/07 14:57
"SpaceGirl" <nothespacegirlspam@subhuman.net> wrote in message
news:dac9060a-6400-4f5d-bd55-d5cb3d1e83d6@e25g2000prg.googlegroups.com...
> I'd seriously consider re-engineering your site.
That's a lot of work for one bug.
> You could could do
> this FAR more efficiently using AJAX, and also remove most of the
> browser issues you're seeing.It'll require much less of a heavy
> workload on the browser, so you'll find it faster and smaller. Also
> you wont be loading in images (shops) that aren't actually visible on
> the screen until they scroll into view, so you'll probably save a
> stack of traffic.
We aren't! Our j/s code is so seamless you don't realise, but the only
shops that are loaded are the ones that are on screen! Try scrolling fast
and you can catch them loading and unloading on demand.
> Again, alternative, do it in Flash.
>
> I'd really go back to the drawingboard on this one - I don't think you
> have a bad idea, but it's very poorly executed. Even if you fix the
> issues you're having now, you'll just hit more down the line (or see
> poor traffic due to errors that users will never bother to report -
> they will just go elsewhere).
Our stats say otherwise.
Thanks for confirming that the site works for you. I do still wonder those
other 2 people's Firefox don't work if yours and every other Firefox we can
find does. Also other people in this thread did not report the issue either
when testing.
Not saying they're wrong, just saying it would be great if someone actually
knew the specific reason, i.e. "this code on this line should read this".
Saying "rewrite the entire site" for 2 users is not ideal I hope you
understand.
Navigation:
[Reply to this message]
|