Closed
Bug 2118
Opened 26 years ago
Closed 25 years ago
OBJECTs degrade incorrectly
Categories
(Core Graveyard :: Plug-ins, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M4
People
(Reporter: Antti.Nayha, Assigned: serhunt)
References
()
Details
(Whiteboard: [OBJECT])
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.
Updated•26 years ago
|
Assignee: amusil → av
Don't forget to implement the attribute TABINDEX for element OBJECT.
Comment 3•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I think we can consider this fixed as to original incorrect behaviour. Should be in after 4.30pm March 10 build.
Updated•26 years ago
|
Status: RESOLVED → REOPENED
Comment 5•26 years ago
|
||
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.
Comment 7•26 years ago
|
||
Crashing in: nsCSSFrameConstructor::CantRenderReplacedElement()
Updated•26 years ago
|
Target Milestone: M3 → M4
Comment 8•26 years ago
|
||
Bumping to M4
Updated•25 years ago
|
Whiteboard: [OBJECT]
Updated•25 years ago
|
Priority: P2 → P1
Reporter | ||
Updated•25 years ago
|
Severity: major → critical
Reporter | ||
Comment 10•25 years ago
|
||
All five tests still crash my April 5th Win32 build. Changing Severity to "critical".
Assignee | ||
Comment 11•25 years ago
|
||
My April 5th build does not crash on either test. I am using checked build though.
Reporter | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 12•25 years ago
|
||
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!
Comment 13•25 years ago
|
||
Awesome!
Comment 14•25 years ago
|
||
will verify when 5363 gets fixed
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 15•25 years ago
|
||
marking as verified, using the 1999042608 build on winNT and checked on win95 too.
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•