300510 - no activity from Flash page

Status: RESOLVED FIXED

(Camino Graveyard :: Plug-ins, defect)

Description

[Dave Lentz]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b3) Gecko/20050710 Camino/0.9a1+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b3) Gecko/20050710 Camino/0.9a1+

The reference URL displays fine under Mozilla 1.7.7 and Safari 2.0, but under
Camino nothing happens, just a blank screen.  Flash plugin version 7.0.24, tests
OK on Macromedia test page, so it's certainly possible that there's something
funny about this particular page -- but Mozilla & Safari display it OK.  No
entries in console log, most obvious symptom is that no/nada/zilch network
activity ensues when the url is entered in the address field -- distinctly
different from other browsers.

Reproducible: Always

Steps to Reproduce:
1. paste http://www.kernelthread.com/publications/osxkernel/osxkernel.swf into
address field
2. press enter
3. there is no step 3!

Actual Results:  
nothing/nada/zilch/bupkiss.  No network activity (I see the request go out, but
that's it), Camino just sits there and blinks at me, as if it's waiting for
something (like a page to be delivered).  I can open new tabs/windows and do
anything else, but it will not load this url.  No crash or other indication of
problem.

Expected Results:  
displayed the SWF page.

Comment 1

[Mike Pinkerton (not reading bugmail)]

how about deerpark or mozilla 1.8? let's compare apples to apples first.

Comment 2

[Dave Lentz]

Works in Firefox [Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.7.8) Gecko/20050511 Firefox/1.0.4] and latest Mozilla NB [Mozilla/5.0
(Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050702].  Flash
page displays correctly.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

WFM, Camino 0.9a1+ (20050710), 10.3.9.

Comment 4

[Mike Pinkerton (not reading bugmail)]

doesnt for me on 10.4 (0.9a1)

Comment 5

[Dave Lentz]

10.4.2 update fixed the problem