Interesting to see this old

webwiz — Thu, 25 Feb 2010 20:45:05 +0000

Interesting to see this old thread revived. I guess the issue of window size - limited as it is by screen size - is becoming more of an issue with new devices like the iPad coming on board.

(The iPad is either 1024px or 768px wide, depending on how you hold it...)

If you feel changing the

prem123 — Thu, 25 Feb 2010 19:57:00 +0000

If you feel changing the layout on resize is a bit too jarring, just remove the second addEvent call to dynamicLayout on resize to limit layout adaptation to occurring only when the web page is first loaded or refreshed by the user. One nice thing about using these functions is that you can easily adapt the code with a little cookie magic to create a better stylesheet switcher to provide your users the choice of what layout option they prefer.

Hmm didn't check Safari...

decibel.places — Tue, 17 Mar 2009 13:55:37 +0000

Hmm didn't check Safari... but you are correct. However, it's only in a problem in a small window for Safari 3.2.2 on Vista, full screen it works okay.

I know it has to do with setting the bottom margin of the main container to -800px (note: greater than the height of the window) - which is necessary because the menu adds extra margin at the bottom of the page because of the menu divs...

I have a hunch it is some kind of z-index issue, not sure.

There is a very similar menu that stores its data in an external JavaScript, not HTML in the body, which probably solves the issue, I will try using that next time.

Bizarre. I have no idea why

webwiz — Tue, 17 Mar 2009 02:24:03 +0000

Bizarre. I have no idea why this happens, though.

FWIW - I see the same behavior in Firefox 2, 3, and 3.1 (Mac) and Safari 3 (Win xp) no matter the window size. (Up to 1680 x 1050 less top OS X menu bar.) Okay in Safari 4 (Mac) though.

greg wrote: So why bother

decibel.places — Mon, 16 Mar 2009 22:29:03 +0000

greg wrote:

So why bother fixing it?
What percentage of the total users who will have this issue will actually come to the site?

Well, the PM keeps his browser in an 800x600 window on his large screen monitor - I convinced him that it is a miniscular problem, but it bothers him, a little.

There is a JS version of the same menus that avoids the divs in the document body, I think that will fix the problem.

I like the menu because it can be attached to any links, such as a very customized image menu, so the top menu item does not need to have the same look as the dropdowns.

But it's a weird problem, only in Firefox, only in an 800x600 window, and only on page load before the mouse is moved over other parts of the page...

decibel.places

greg — Mon, 16 Mar 2009 21:17:00 +0000

decibel.places wrote:

Realizing that we are probably talking about a fraction of a percent of viewers, and even then the problem "goes away" before most people would notice it

So why bother fixing it?
What percentage of the total users who will have this issue will actually come to the site?

I know I know, you want it working as desired, and if it was something that broke the entire page or a lot of layout then I would perhaps understand.

So for the sake of what, about 34 people in the world with firefox in 800x600 have a brief issue with links?

Besides, no monitors will actually HAVE 800x600 by the time I have looked through all that code