Closed Bug 178609 Opened 24 years ago Closed 24 years ago

setting display style property to none: dodgy behaviour

Categories

(Core :: Layout: Tables, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 97506

People

(Reporter: yoda, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 It seems that setting an object's 'display' property to 'none' dynamically causes some display glitches, that are contrary to behaviour when specifying that property setting when the page first loads. Reproducible: Always Steps to Reproduce: 1. Have a look at supplied URL. 2. For each heading (with an expand (+) sign next to it), there is a row directly below it that has the CSS 'display' attribute set to 'none'. All looks fine and dandy. 3. Click one of the + symbols. Now collapse that category again. 4. Things don't look the same as they were - the row is gone, but the space it reserved is still there, although when the page first loaded there was nothing showing of it at all. Actual Results: There are great big ugly spaces after using the page. Expected Results: I would have thought that the row, and the space it reserved when it was visible, should disappear altogether. The inconsistency of behaviour between the initial loading of the page and when setting the display property dynamically seems to suggest a bug to me ...
> d.style.display = (bDisplay ? "block" : "none"); Oops. Setting display to "block" on a table row (the correct value is "table-row" is a bad idea in general (and yes, we have some issues in handling it). This is a dup of one of the bugs blocked by bug 162063...
Assignee: jst → table
Component: DOM Style → Layout: Tables
QA Contact: ian → amar
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 97506 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.