207435 - <MARQUEE /> rendering with very minimal width, instead of "full" width

Status: RESOLVED FIXED

(Core :: Layout, defect)

Description

[Serge Gautherie (:sgautherie)]

User-Agent:       Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4b) Gecko/20030507

I provide the URL on which I first encontered the issue;
but it may not be permanent;
anyway, I'll attach a very reduced testcase in the next comment.

This bug depends on the very reduced html code _around/outside_ the marquee
section !


Reproducible: Always

Steps to Reproduce:
1. In Mozilla, Load the testcase
2. Outside Mozilla, Edit it to remove either the "<FONT />", or the "&nbsp;"
3. In Mozilla, Reload the testcase

Actual Results:  
At step 1, the marquee width is a few pixels only; (BROKEN)
At step 3, the marquee width is "full window". (correct)


Expected Results:  
Step 1 should display (almost) like step 3.


Somehow, it's the opposite of bug 207340 (part 2) where the width rendering is
too wide.


[Netscape® Communicator 4.8 : en-20020722]

The width is correct (even if v4.8 does not scroll): I'll add '4xp'.


[Microsoft Internet Explorer, version 3.0 (4.70.1158)]

Works correctly: width (bgcolor and scrolling).

Comment 1

[Serge Gautherie (:sgautherie)]

Attachment: Very reduced testcase, based on bug URL page

Comment 2

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.3.1) Gecko/20030425]

This bug was already there.

Comment 3

[Jesse Ruderman]

Attachment: another testcase

based on http://studentpages.scrippscollege.edu/~hhight/

Comment 4

[Doron Rosenberg (IBM)]

fixed

Comment 5

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040316] (W98SE)

<http://www.caisse-epargne.fr/asp/modele2.asp?np=sic_cappuccino&nv=20030515173535&cleMagic=42>
from comment 0, is no longer valid.

(for the record)
Not fixed in v1.7b.
Fixed in future v1.7 !? by fix for bug 167224 ??

Comment 6

[u81239]

*** Bug 241988 has been marked as a duplicate of this bug. ***