Closed
Bug 54347
Opened 24 years ago
Closed 23 years ago
table "jumps" when chaning bgcolor via javascript
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: karnaze)
References
()
Details
Attachments
(2 files)
This bug is pretty weird, but here we go: If you go to: http://gemal.dk/util/bgcolor.html and note when the top table start. Now press on one of the colors and watch the entire table jumps a bit up.
Reporter | ||
Comment 1•24 years ago
|
||
Comment 3•24 years ago
|
||
Good news and bad news: First the good news, the problem is not with changing the bgColor, it is with these two lines of script: document.color.colorname.value = ColorName; document.color.colorrgb.value = ColorRGB; Remove them and no jumping. I dont know what those lines are suppossed to do, so please explain and I'll try to direct the bug toward the correct module. Bad news: The test page looks positively awful in NS6 B3 (build from 9-29). It looks much nicer in Nav4. In Mozilla, each color square is large and has text in it, in nav they are nice and small and have no text. I'm CC'ing buster since I believe this may have to do with MAP / AREA handling... Buster, please check this site out and see if related to MAP changes.
Comment 4•24 years ago
|
||
Actually, never mind Buster, I'm pretty sure this has nothing to do with MAPS, but rather the ALT attribute. sorry, I jumped the gun.
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
Chris, this sure looks like an incremental reflow problem with tables. Note that in the attached local copy of the page I removed the bgcolor from the <BODY> so now you have to pick 2 colors before it jumps - strange. Also, the comments I made on the 29th all appear to be bogus - must have had a bad lunch ;) Sorry I cannot narrow this down further for you.
Assignee: attinasi → karnaze
Reporter | ||
Comment 7•23 years ago
|
||
seems to be fixed in todays build.... 20010302...
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•