[CSS] weird <div> behaviour in firefox

[SBmx]

hello,

please take a look at this page:
http://odradek.net/jla/html/accordeon.html

by selecting items on the left one can expand and collapse sublists on
the right. this is very run-of-the-mill dhtml stuff: the links on the
left change the display property of the <div>'s in which the lists are
nested.

it works fine on most browsers, but in firefox some of the list <div>'s
do not cause the table cells in which they are embedded to expand the
way they should, thus causing ugly overlaps. the layers with this
erratic behaviour are always different ones, sometimes it's only one of
them, sometimes three, sometimes all...

this apparent randomness leads me to believe that it must be some kind
of bug or bad implementation in firefox, but i couldn't find any
documentation on this.

anyone have suggestions, workarounds or fixes?

thanx

sbmx

 

[Els]

http://odradek.net/jla/html/accordeon.html

by selecting items on the left one can expand and collapse sublists on
the right. this is very run-of-the-mill dhtml stuff: the links on the
left change the display property of the <div>'s in which the lists are
nested.

it works fine on most browsers, but in firefox some of the list <div>'s
do not cause the table cells in which they are embedded to expand the
way they should, thus causing ugly overlaps. the layers with this
erratic behaviour are always different ones, sometimes it's only one of
them, sometimes three, sometimes all...

this apparent randomness leads me to believe that it must be some kind
of bug or bad implementation in firefox, but i couldn't find any
documentation on this.

anyone have suggestions, workarounds or fixes?

AFAICS it works fine in my version of Firefox (1.5.0.7 on WinXP)

 

[Jonathan N. Little]

AFAICS it works fine in my version of Firefox (1.5.0.7 on WinXP)

Ditto for Firefox 2.0 on Win2k and SeaMonkey 1.0.5

 

[David Woods]

hello,

please take a look at this page:
http://odradek.net/jla/html/accordeon.html

by selecting items on the left one can expand and collapse sublists on
the right. this is very run-of-the-mill dhtml stuff: the links on the
left change the display property of the <div>'s in which the lists are
nested.

it works fine on most browsers, but in firefox some of the list <div>'s
do not cause the table cells in which they are embedded to expand the
way they should, thus causing ugly overlaps. the layers with this
erratic behaviour are always different ones, sometimes it's only one of
them, sometimes three, sometimes all...

this apparent randomness leads me to believe that it must be some kind
of bug or bad implementation in firefox, but i couldn't find any
documentation on this.

The problem, I believe, is with your JavaScript on the Solo/Small Ensemble
link. It fails to close/hide/whatever the contents of links below it that
have been previously opened.

 

[Jonathan N. Little]

The problem, I believe, is with your JavaScript on the Solo/Small Ensemble
link. It fails to close/hide/whatever the contents of links below it that
have been previously opened.

No it is the one above that is the problem. All others expand the left
column to match the right when expanded. But the first, ORCHESTRA, does
not so when any of the sections below are expanded it overwrites ORCHESTRA

 

[Jonathan N. Little]

No it is the one above that is the problem. All others expand the left
column to match the right when expanded. But the first, ORCHESTRA, does
not so when any of the sections below are expanded it overwrites ORCHESTRA

Actually that was with SeaMonkey so akin to Firefox 1.5.0.7, but with
Firefox 2.0 I get the above problem on different sections, "SOLO / SMALL
ENSEMBLE" and "VOCAL / CHORAL"! I suspect you have some markup errors.
Yep I see a couple.

Line 76 & 77

</tr>
</tr>

two closing TRs???

BTW the HTML element cannot have a STYLE attribute:
http://www.w3.org/TR/html4/struct/global.html#edef-HTML

 

[SBmx]

The problem, I believe, is with your JavaScript on the Solo/Small
Ensemble

column to match the right when expanded. But the first, ORCHESTRA, does
not so when any of the sections below are expanded it overwrites ORCHESTRA

like i said, the problem appears on other lists everytime i reload the
page. apparently completely at random.

sbmx

 

[Jonathan N. Little]

like i said, the problem appears on other lists everytime i reload the
page. apparently completely at random.

Did you fix your markup errors? I pointed out one on Line 77 you have an
extra </tr>. If you throw invalid markup at a browser is will be
unpredictable in its presentation as it tries to "make sense" of the
antiquity.

 

[Jonathan N. Little]

Did you fix your markup errors? I pointed out one on Line 77 you have an
extra </tr>. If you throw invalid markup at a browser is will be
unpredictable in its presentation as it tries to "make sense" of the
antiquity.

Let's try the correct work shall we! "ambiguity" !!!

 

[dorayme]

Did you fix your markup errors? I pointed out one on Line 77 you have an
extra </tr>. If you throw invalid markup at a browser is will be
unpredictable in its presentation as it tries to "make sense" of the
antiquity.

The antiquity!

 

[dorayme]

Let's try the correct work shall we! "ambiguity" !!!

work!

 

[Jonathan N. Little]

The antiquity!

That's what I get for using spell-checker and dashing it off before
*really* proofing. Damn my cursed spelling handicap, I am doomed,
doomed, doooooomed I say!

 

[SBmx]

Did you fix your markup errors? I pointed out one on Line 77 you have an
extra </tr>. If you throw invalid markup at a browser is will be
unpredictable in its presentation as it tries to "make sense" of the
antiquity.

you were right of course, after cleaning up the page and making sure
everything validates properly the problem seems to be solved ...

thanks a K!

..sbmx

 

[Jonathan N. Little]

Did you fix your markup errors? I pointed out one on Line 77 you have an
extra </tr>. If you throw invalid markup at a browser is will be
unpredictable in its presentation as it tries to "make sense" of the
antiquity.[ambiguity] sp.

you were right of course, after cleaning up the page and making sure
everything validates properly the problem seems to be solved ...

Yes if you find yourself with a transient presentation anomaly, start
digging for a markup error! It is one of the reasons is still keep a
copy of Netscape 4.6 installed, it a miserable CSS support but it sure
can signal a markup error! No real attempt to "interpret", it just bombs!

 

[dorayme]

Yes if you find yourself with a transient presentation anomaly, start
digging for a markup error! It is one of the reasons is still keep a
copy of Netscape 4.6 installed, it a miserable CSS support but it sure
can signal a markup error! No real attempt to "interpret", it just bombs!

Safari is a bit like this in that it is not very fault tolerant.
iCab is marvelous in having the little face which only smiles on
the truly valid, the mensch of the webpage world...