Closed Bug 300909 Opened 19 years ago Closed 16 years ago

On Hover, tbody rows are displayed - on un-hovering, display:none hides tbody rows but real estate is maintained, accumulatively.

Categories

(Core :: Layout: Tables, defect)

1.7 Branch
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gusrichter, Unassigned)

References

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5

When moving the cursor over the table, tbody rows are displayed. When the cursor
is moved off the table, the tbody rows are no longer displayed, but the space
which was occupied is wrongly maintained. Repeating the hover procedure causes
the maintained space to be increased each time.

Reproducible: Always

Steps to Reproduce:
1. Bring up the demo/example with Firefox.
2. Hover over the three tables to see their effects.
3.

Actual Results:  
The demo/examples show the problem clearly.
Look at the semo/examples with Opera to see the proper behavior.
display:inline and display:table maintain and accumulate previous space.
display:table-row behaves properly but removes borders.



Expected Results:  
This is a CSS problem which should behave as seen with Opera.
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → 1.0 Branch
very similiar to bug 206516
Component: Layout → Layout: Tables
QA Contact: layout → layout.tables
Depends on: 162063
Keywords: testcase
Version: 1.0 Branch → 1.7 Branch
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'll take comment 2 to mean "a fix for bug 206516 might fix this too" and mark a dependency so we remember to retest this variant when that one's done.
Depends on: 206516
the remaining pixel shift is bug 162063
Tested with Win/Fx 3.01 and problem is no longer present.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
If you don't know what specifically fixed it, the proper resolution is WORKSFORME.
Resolution: FIXED → WORKSFORME
(In reply to comment #6)
> If you don't know what specifically fixed it, the proper resolution is
> WORKSFORME.
> 
Thank you.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: