Weird display bug

[TheHYPO]

latest version (v. 1.3.8a I believe it is), IE6.

I found this bug while working on some modifications to my own template, but was able to quickly replicate it using the Classic Green default template (for those of you who might need to reproduce it to diagnose or fix the bug)

Using only left-side sideboxes (don't use right side, may also be problematic in 2-sided boxes)
Using new items index-page box module with FOUR items per column (other numbers may also be issues)
Using featured items index-page box module with FOUR items per column:
(note: on my site, new products is first, then featured - order may impact which box is affected)

in class .leftBoxContainer, .rightBoxContainer
Commenting out the border (or setting the border to 0px) results in a screwup of the featured product index box when you have the store set to display a column of 4 items (I have a wider mainWrapper than default, and have a 4x grid for those index page boxes). The 4th item of each row ends up alone on the next row (sometimes under the first, second or third spot in the previous row).
I have narrowed it down to the left and right borders - top and bottom borders do not have effect. When I used only one of the two side borders (only left or only right), the featured box seemed to display correctly, However, the "new products" box then has a similar problem.


I have presently bypassed the issue by including 1px left and right borders of the same colour as the background. However, I'm not sure exactly why the borderon the sideboxes messes up the alignment of the centre boxes, but there you go.

(in case anyone is wondering, the reason I would want no border for that class is that I decided to have the heading boxes of each sidebox have its own border, and then just a border of another colour for the rest of the box - to do this, I created a new div around the box's content which has a css border on sides and bottom, leaving the wrapper around the entire box with a desired no-border. This change is in my own template however, and the bug appears in Classic Green, so nothing I did should have caused the bug.)

[yellow1912]

A link to your site will help us to debug it.

[TheHYPO]

It would be, but whereas I am still building the site, I can't really publicize the URL; that's why I tested it on the default Classic Green template, which means it <i>should</i> be reproducable to anyone.

[DrByte]

You posted another topic which appears to be related to this one, but with a different desired twist on it. Some ideas have been posted there, which might help.
http://www.zen-cart.com/forum/showthread.php?t=85883

[TheHYPO]

Yeah, I thought I was done with this bug using the above fix, and was just posting to let people know for a suggested investigation for future fixing, but as I continued customizing, I found that also centreWrapper (I think its called) - deleting the side borders on the centre boxes had the same effect, leading me to just get really pissed off with the bug's making it imposible for me to properly customize the look of the store, and also never being sure it wouldn't end up recurring with a long-named product or anything else, so I decided to do something about it myself even though I know the consensus seems to have somehow changed in the last five years to be that DIVs beat tables for virutally any application. I still far prefer tables' static assuredness of position when doing layout (if I have three TDs in a row, I don't ever have to worry about the last TD ever floating below the other two to mess up my layout.

Don't get me wrong - when people want things like images floating in the corner on their product info page with the description text wrapping around it, DIV float is great for that, but I think overkill was taken in going to DIVs as the standard.

But that's my 2 cents outside the pervue of this problem. Thanks for taking the time to check, and I hope this post might be helpful in addressing the bug in future releases

[kuroi]

I suspect from the description that you're describing the problem discussed (with fix) in this thread. Post 6 is the one to scoot over to.