NGLayout nightly build (Dec-31) degrades OBJECT elements incorrectly. For example: if the OBJECT has width=100 and height=100, the alternative content is also forced into this space. The size of the alternative content should *not* be dependent in any way on the OBJECT element's width and height attributes. See the URL for several examples of this behaviour and the problems it causes.

Don't forget to implement the attribute TABINDEX for element OBJECT.

Setting all current Open Critical and Major to M3

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

I think we can consider this fixed as to original incorrect behaviour. Should be in after 4.30pm March 10 build.

attempted to access the above URI, selecting any of the test from that page and the 3/16, apprunner build crashes: APPRUNNER caused an invalid page fault in module RAPTORHTML.DLL at 014f:01059675. Registers: EAX=00000000 CS=014f EIP=01059675 EFLGS=00010246 EBX=009ec170 SS=0157 ESP=0076fb48 EBP=0076fb9c ECX=0076fb8c DS=0157 ESI=0109d878 FS=0e8f EDX=816be444 ES=0157 EDI=008f6a90 GS=0000 Reopening bug until the crashing is resolved. I suspect we have more OBJECT element related issues.

Could be not OBJECT tag related. I noticed, it does not crash on all tests except #4 if the Viewer window is large enough. Just maximize it first. Maybe general layout problem. I am adding troy and nisheeth to the cc list.

Crashing in: nsCSSFrameConstructor::CantRenderReplacedElement()

Bumping to M4

I do not see crash any more

All five tests still crash my April 5th Win32 build. Changing Severity to "critical".

My April 5th build does not crash on either test. I am using checked build though.

My apologies, it seems that I was using an old March build by mistake. The extracting directory in the new nightly .zip's seems to have changed, which confused me. My April 6th build _does_ pass the alternative renderings test - it's actually the first OBJECT-supporting browser to do so. Congrats to everyone involved!

Awesome!

will verify when 5363 gets fixed

marking as verified, using the 1999042608 build on winNT and checked on win95 too.