Topic awaiting preservation: troubles with ozone's zscrollbar (Page 1 of 1)

ok guys, i'm using ozone's zscrollbar 2 right here http://www.thespacebetweenus.com/index1.php

my problem is that it stops scrolling at a certain point and i don't know why. scroll down there, then you will see that it stops @ "weadah where are you?", but there are still 2 or 3 news articles below it

how can i remove this bug? please help me!

elysiumart

That's strange... I'm seeing two articles below the one about Weadah. What browser are you using when you see the problem?

WHAT? REALLY?

i'm using IE 6.0

a friend of mine got the same problem.

edit: ah strange...ir works in mozilla
edit2: i think the problem is, that it only scroll a certain amount of pixels;when i small down the fonts, it scroll further.

[This message has been edited by mas (edited 02-15-2003).]

[This message has been edited by mas (edited 02-15-2003).]

Now this is even stranger. I just went back to the page to see it and now it is doing what you said. I do not know why. I'm using IE 6.0 too.

but who could know?

Well, it's ultimately Doc's code. I don't usually look too close at his stuff so I can stay independent in my coding but Slime and bitdamaged are awfully good at this stuff. I'm taking a closer look now to see if anything jumps out at me.

thank you very much.well i don't try to ask doc because i think he is too busy anyway...well slime isn't online at the moment, i know that he is perfect @ JS, like you.

damn do you know what's really strange? if i change my resolution from 1152 to 1024(same happens when i switch back) then everything works fine. but at the moment when i hit the refresh button, the bug appears.

[This message has been edited by mas (edited 02-15-2003).]

I just maximized the browser window and the bug went away. But as soon as I refresh it comes back. Hmm... this is very interesting.

Doc's setup function is tied to the onresize and onload events. By resizing, I'm calling setup after the initial load and that seems to be the one that is clearing up the problem but I don't understand why it doesn't get all the dimensions sorted out when the onload event fires.

aha......ok...i don't really understand what this means but......do you know a solution?

I'm very sorry, mas, but I'm just not seeing what exactly is wrong here. I know Doc's stuff works and I can't see where what you have deviates from what his code expects. Does his stuff come with any special guidelines and did you follow everything it says? I'll try again tomorrow if someone else hasn't helped you by then.

thanks anyway, bugs. well there are a few settings you can adjust but there is nothing about the length it scrolls. and man....it works in mozilla

mas: An old bug indeed (no offense to bugs ).

So lets run through what is happening:

1. When it loads it works fine.

2. If you refresh or come back to the page the scroller is too short.

3. If you resize the page the problem is fixed.

So try and find the bits thatfire onload and on resize and the bits that get the length of the area to scroll. Sorry I can't be more help but the problem may be somewhere in there.

___________________
Emps

FAQs: Emperor

thx emps, but i have thought of something like this before, but i can'T find it
oh, btw it DOES NOT work in mozilla too. my mistake, sorry

edit: i have found these two tags at the very end of the zscrollbar2.js file

it just says:

//Important! Don't delete this next bit...

onload=setup;
onresize=setup;

that's it

[This message has been edited by mas (edited 02-16-2003).]

I remember a similar thing coming up over at the GN before. You might want to check over there to see if anyone found a solution.

I do have a couple of suggestions though, try adding this line to the "Don't delete next bit..."

window.onfocus = setup;

That should fix the switching back to the page bug. If your still having issues with it onload set a small setTimeout in the setup() function to call itself again. Something like:

var doubleCheck = 0

setup() {

doc's code...
doc's code...
doc's code...

if (!doubleCheck) {doubleCheck = setTimeout("setup()",100)}

}

It seems odd but it's fixed some elusive oddities for me from time to time. Oh, this is all assuming that running the setup() function will fix the bug.

Although It may be a standards thing too. You have <?xml version="1.0" encoding="iso-8859-1"?> in your document but no <!doctype> ???... Anyways, IE5.5 and 6.0 act differently when in "standards" mode (when there's a <!doctype> present, although the <?xml> might also be forcing it into standards mode) in not only how they display CSS but how you access it through the DOM. In standards mode all the element that we once accessed through document.body get moved to document.documentElement which is a ripe pain in the rear end at the best of times.

But from memory Docs scripts didn't work well in strict standards mode as he wasn't adding + "px" like values when assigning properties, yet another thing IE likes to change. *grumble* But if you to make the script work with a strict standard then you'll need to add them in. Anyways, let us know if those fixes work.


[This message has been edited by Dracusis (edited 02-17-2003).]

yepeee window.onfocus = setup; did it, man!

Great catch, Drac!!!