271419 - Strange drop-down menu behavior

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, defect)

Description

[Alexander Doborshhuk]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041122

When choosing category, subcategory menu sometimes just freezes, or needs
several clicks and keyboard operations to show up. And subcategory menu for some
reason messes up and appears above the category menu...
Firefox 1.0 and IE works flawless there.

Reproducible: Always
Steps to Reproduce:
1. Load page
2. Choose some category
3. try to choose some subcategory

Actual Results:  
Menu messed up or not loads

Expected Results:  
..

Smoke Theme

Comment 1

[Hermann Schwab]

open JS console and see a lot of CSS errors, like:
Error: Expected end of value for property but found 'margin'.  Error in parsing
value for property 'padding'.  Declaration dropped.
Source File: http://s.deviantart.com/styles/napalm.css/2821.css
Line: 570

Error: Unknown property 'hhheight'.  Declaration dropped.
Source File: http://s.deviantart.com/styles/napalm.css/2821.css
Line: 1212

Error: Expected 'important' but found 'impotant'.
Source File: http://s.deviantart.com/styles/napalm.css/2821.css
Line: 1257

Warning: test for equality (==) mistyped as assignment (=)?
Source File: http://s.deviantart.com/styles/love.js/2821.js
Line: 189, Column: 28
Source Code:
	while(Node=Node.nextSibling)


W3C CSS-Validator:
http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fs.deviantart.com%2Fstyles%2Fnapalm.css%2F2821.css&usermedium=all

Comment 2

[Martijn Wargers (dead)]

Attachment: Not entirely minimised testcase

The <legend> inside a <fieldset> is changed to display:block. That seems to
cause this bug. 
Maybe this is also fixed by the patch for bug 276104?

Comment 3

[Jesse Coddington]

Check out the comments by Peter(6) at this link:
http://forums.mozillazine.org/viewtopic.php?t=195846#1124907

Comment 4

[Noah (NoahSUMO/SolidSnake) [:Noah]]

And correspondingly this one, per Warforge,
http://forums.mozillazine.org/viewtopic.php?p=1125174#1125174

Comment 5

[Boris Zbarsky [:bzbarsky]]

Note that martijn's partially minimized testcase doesn't have any comments in
it, so either the comments are a red herring or there is more than one issue here.

Comment 6

[Peter van der Woude [:Peter6]]

(In reply to comment #5)
> Note that martijn's partially minimized testcase doesn't have any comments in
> it, so either the comments are a red herring or there is more than one issue here.
I think the "</select-->" is the problem.
removing the whole comment part makes the faulty select work again.

Comment 7

[Martijn Wargers (dead)]

Attachment: Testcase2, minimised

This one is minimised.

Comment 8

[Boris Zbarsky [:bzbarsky]]

Yeah, the patch in bug 276104 should help with that....

Comment 9

[Joël Kuiper]

It's not a problem with the <!-- --> as testcase2 indicates...

Comment 10

[Peter van der Woude [:Peter6]]

(In reply to comment #9)
> It's not a problem with the <!-- --> as testcase2 indicates...

Indeed, sorry for that.
It did because my cache refused to clear again.

Comment 11

[Noah (NoahSUMO/SolidSnake) [:Noah]]

Well, how about the theory Ger Teunis describes?
http://forums.mozillazine.org/viewtopic.php?p=1125252#1125252

Comment 12

[Mats Palmgren (inactive)]

The category menus at the URL and testcases now works fine (fixed by bug 276104).
I can see one problem still at the URL, when changing "Any Time" to
"Specific Date" the surrounding container sometimes does not resize properly
(incremental reflow problem).
A reduced testcase for that would be appreciated.

Comment 13

[Martijn Wargers (dead)]

Attachment: Testcase3, not minimised yet

You get to see the bug when changing "submitted" to "Today".
Note the <div style="overflow: hidden; clear: left;"> surrounding the content.
When I remove that, then the bug is not visible anymore.

Comment 14

[Mats Palmgren (inactive)]

Thanks Martijn, I reduced it further and saw that it was a table issue so
I spawned it off as bug 279832.

The original problem here was fixed by bug 276104.

-> FIXED