Closed Bug 309163 Opened 19 years ago Closed 19 years ago

Macromedia Flash content is not loading and is not visible.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: vschristopher, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

The latest Beta Version of Firefox is not loading Flash content for eg
www.eye4u.com flash content and flickr.com flash based interface tools.

Reproducible: Always

Steps to Reproduce:
1.Open any flash based website for eg TribalFusion.com
2.The flash content doesn't load/displays.
3.Thats it

Actual Results:  
Nothing

Expected Results:  
Should have loaded the flash movie/interface.
Severity: normal → major
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050916 Firefox/1.4

This is WFM on the example URL and others.  You have got Flash installed
(about:plugins), I assume?
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050919
Firefox/1.4 ID:2005091911

WFM
Please check that you do not have the adblock extension with object tabs, see
bug 308918.
No really, I don't have adblock and object tabs, and flash still doesn't load. 
On more than one machine.  This is a deal breaker before release, as EVERYONE I
know is on myspace.com, and that requires flash for many functions.  I also
tried Flash 7 and Flash 8, to no avail.
I agree I have tried downloading the flash plug in for beta 2 it doesn't work I
cannot see any flash enabled objects on any website.  I check it off of IE and
they all work there on the same sites side by side.  
TribalFusion.com
www.eye4u.com

Both WFM with
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051103 Firefox/1.6a1
Shockwave Flash 8.0 r22
No extensions
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.