OBJECTs degrade incorrectly

VERIFIED FIXED in M4

Status

()

P1
critical
VERIFIED FIXED
20 years ago
20 years ago

People

(Reporter: Antti.Nayha, Assigned: serhunt)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [OBJECT], URL)

(Reporter)

Description

20 years ago
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

20 years ago
Assignee: amusil → av
(Assignee)

Updated

20 years ago
Status: NEW → ASSIGNED

Comment 1

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

Comment 2

20 years ago
Setting all current Open Critical and Major to M3

Comment 3

20 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
(Assignee)

Updated

20 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee)

Comment 4

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

Updated

20 years ago
Status: RESOLVED → REOPENED

Comment 5

20 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.
(Assignee)

Comment 6

20 years ago
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

20 years ago
Crashing in: nsCSSFrameConstructor::CantRenderReplacedElement()

Updated

20 years ago
Target Milestone: M3 → M4

Comment 8

20 years ago
Bumping to M4

Updated

20 years ago
Whiteboard: [OBJECT]

Updated

20 years ago
Priority: P2 → P1

Updated

20 years ago
Resolution: FIXED → ---
(Assignee)

Comment 9

20 years ago
I do not see crash any more
(Reporter)

Updated

20 years ago
Severity: major → critical
(Reporter)

Comment 10

20 years ago
All five tests still crash my April 5th Win32 build.
Changing Severity to "critical".
(Assignee)

Comment 11

20 years ago
My April 5th build does not crash on either test. I am using checked build
though.
(Reporter)

Updated

20 years ago
Status: REOPENED → RESOLVED
Last Resolved: 20 years ago20 years ago
Resolution: --- → FIXED
(Reporter)

Comment 12

20 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

20 years ago
Awesome!

Comment 14

20 years ago
will verify when 5363 gets fixed

Updated

20 years ago
Status: RESOLVED → VERIFIED

Comment 15

20 years ago
marking as verified, using the 1999042608 build on winNT and checked on win95
too.
You need to log in before you can comment on or make changes to this bug.