Preserved Topic: Little help please (Page 1 of 1)

Hi guys

I would really appreciate it if someone would take a look at this page and help me find out why my divs don't switch when you click on the page number links at the bottom. They worked before, and now they don't, and I can't figure out why.

I've checked my CSS and my PHP script and I don't believe the problem is in the code in either of those. I'm hoping it's something obvious that I'm just not seeing because I've been looking at it for too long.

I'm hoping a fresh pair of eyes (that knows a little more about JS than I do) can pick out the problem.

Thanks in advance



- Resolutions, Of All My Fruitless Searches -

Hm. They ARE switching!
On E5 at least.

Argh!!!!

Your right, I checked my page in Netscape, and they do switch. This means I need to rephrase my question.

Does anyone know why the JavaScript on the page listed above doesn't work in IE 5.5, but does in NN4.7 and IE 5.0? I check the JavaScript settings in my IE and it says enabled, so I don't think that's the problem. I'm not doubting it could be local, because this just started a day ago, untill then it worked fine, but I don't think I did any thing to change it.

Thanks

Thanks again.

- Resolutions, Of All My Fruitless Searches -

Well, butcher, I checked you rsite AND... I can;t help you..
why don't you ask the www.xeo.com guys? they programmed it, right?

but it IS a nice site... I like it
k10


only change remains

Thanks for looking, and the compliment, but no the xeo.com guys didn't program it, they wrote the java applet for the sliding nav links thingy on the left side. I was asking about the page links at the bottom of the page.

BTW it must have been local, I reinstalled IE 5.5 and it works fine for me now too.

Thanks for your help

- Resolutions, Of All My Fruitless Searches -

Well, FWIW, they worked OK in IE5.5 for me earlier, but when I went to test in NN6, your page crashed my OS (Win98). I think that applet's a bit dodgy. I tried again in NN6 after reboot, and get null pointer exception out of your applet, and the DIVs don't swap as a bonus.

I think the DIV swap is breaking in because you're using Macromedia/Dreamweaver swap functions, and I don't know how out of date they are. Maybe it's a good opportinity to code your own. Just don't look at the ones you have--they are written for compactness, not optimal style. Dunno how concerned you are about NN6.

You could (should?) probably do the navigation control thing with DHTML and avoid the applet madness.



[This message has been edited by linear (edited 06-11-2001).]

Man Linear

You must have been able to hear that little voice in the back of my head (that I've been ignoring nicely till now) that's been trying to tell me the same thing about writing my own JavaScript for the div swap.

I've had the thought, but I was being lazy. I was so pitiful at trying to learn JavaScript the first time around, that I've been avoiding it. It's probably the next thing I'll tackle.

I've noticed NN4.7 having a little trouble from time to time with the applet, but it seemed to run it most of the time, so I was going to let it go. I guess I'll have to break down and get NN6 on my machine and do some testing.

Thanks for sharing the good news Linear.

- Resolutions, Of All My Fruitless Searches -

[This message has been edited by butcher (edited 06-11-2001).]

I know you didn't ask, but...

Win IE 5.5

When I go to your page, then resize my window in the vertical direction, the alignment of your div gets all out of wack...
I am working on a HUGE monitor (2560x1024) so the effect may be more obvious, but I would guess that it could be recreated on any monitor. Just a little FYI.

mobrul

Thanks mobrul

I just tried it at the highest res my machine will go 1024x768 on a 15" monitor, and it wouldn't budge. I guess I need a new vid card and monitor soon. Although I don't think there are too many people out there surfing the web at a res that high, it would certianly be nice to test for it.

Thanks

- Resolutions, Of All My Fruitless Searches -

I have done some experimentation and have recreated the 'bug' at 1024x768.
If you'd like to follow along at home:
1)Open Butcher's page
2)Make your window a small, thin sliver. Width doesn't matter, it's height we're talking about here.
3)Move the window to the top of your screen.
4)Scroll the window until you can see the 4 blue 'links.'
5)Click on one of them. (I choose link 1)
6)Drag the window to be the tallest you can make it.
7)Watch the area where the text div and the title/page heading meet. The text div creeps up into the title graphics.

Maybe if one has to work so hard to find the 'bug' it's not really worth fixing...I don't know. I found it, maybe someone else will too. Do with it as you please.

mobrul

It's worth fixing. I believe that the position of the DIV with the content would need to be recalculated every time the window gets resized. I haven't looked at the source, but any vertical resizing of the window makes the content DIV go strange for me under IE 5.5/Win (1600x1200, but I browse with a smaller window).

Heh, we found bugs you weren't looking for.

I don't know

I have the div that the layers are wrapped in set to be relative (I assume it's relative to the <td> tag it's in). All the nested layers are position: absolute; to the div wrapper.

If the <td> tag moves with a browser resize, shouldn't the whole shootin match go with it?

- Resolutions, Of All My Fruitless Searches -

I think you're misinterpreting what absolute positioning does. I still haven't studied the code ( ), but I'm pretty sure there's no longer a need to have your DIV be absolutely positioned in order to manipulate its visibility.

Bottom line, it's a fixable problem.

i'm on mozilla 0.9.1 and nothing happens while clicking on one of the links

Linear

When I said "I don't know", it wasn't about whether I should fix it or not, it was I don't know quite where to start.

I don't think I explained my code very well.

The divs that are 'position: absolute', are nested in a parent div wrapper that is set to 'position: relative'. It's my understanding (limited though it is) that my parent div needs to be set relative so it moves with the page, and the child divs need to be absolute to the parent so that they move with it.

If that's not correct, I would be greatful for a correction.

u-neek:
Which link?

Thanks guys


- Resolutions, Of All My Fruitless Searches -

butcher:
I read something about this yesterday night and as I read through your problem I thought it was a deja-vu.
You are right. absloute positioning is relative to the window coordinates. relative-positioning would be relative to the wrap around the object (that could be table, div and so on. But also the window if the object is not wrapped).

As I understand, we are talking about problems while resizing, right?
guess what, my version (IE 5.50) doesn;t resize it at all, just makes the window smaller!
k10