Tested with yesterday's build on the Mac (I'm going to verify it on Windows after filing the bug). When an originally invisible absolutely positioned block element is made visible, it is clipped to its parent (it's as if the 'overflow' were set to 'hidden'). This is wrong: the element should be entirely visible. Note that the bug only happens at the time the element is made visible. If you cause a reflow or even just cause an update of the area, the element becomes fully visible. I'm going to attach a testcase (derived from bug 31299).

The bug happens on Win98 too. Changing Platform to All.

kevin has been doing a lot of work in this area. Is this a dup of a bug you already have, Kevin?

I am seeing this problem on WINNT as well. My guess is the logic to invalidate in nsViewManager2::SetViewVisibility is not invalidating the entire view bound's when going from hidden to visible.

This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.

Upon managerial request, adding the "testcase" keyword to 84 open layout bugs that do not have the "testcase" keyword and yet have an attachement with the word "test" in the description field. Apologies for any mistakes.

Works for me. 2001-04-09-04, Win NT.

Build moving all existing future-P3 bugs to future-P4.

worksforme too.