Closed Bug 61196 Opened 25 years ago Closed 25 years ago

Page doesn't render properly without .swf file

Categories

(Core Graveyard :: Plug-ins, defect, P3)

x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rodd, Assigned: serhunt)

Details

When you first load a page that has an embedded .swf file that isn't actually where it should be (ie. missing) the page doesn't render properly. All all the content (except the .swf file of course) seems to be present, but the lines do not wrap. If your hit reload, the page renders properly, with all the lines wrapping accordingly. Below is the tags we're using to embed the flash file into the page: --------------------------------START----------------------------- <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=4,0,2,0" width="329" height="198" > <param name=movie value="images/rituals.swf"> <param name=quality value=high> <embed src="images/rituals.swf" quality=high pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="329" height="198" ></embed> </object> --------------------FINISH------------------------- I've included this in case there is something we are doing wrong with the tags, however, this page renders properly in everything except Mozilla. I'm using mozilla 2000112106-Mtrunk and have been noticing this for a couple of months now.
--> plugins
Assignee: asa → av
Component: Browser-General → Plug-ins
QA Contact: doronr → shrir
Reporter is this still a problem in the latest nightlies?
This is working properly now. The page now renders as expected and leaves a placeholder where the swf file should be. In case it's important, I've tested this on build 2000121706-Mtrunk
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
looks fine on 2001011606 trunk on linux. Marking VERIFIED.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.