Closed Bug 110537 Opened 23 years ago Closed 23 years ago

Quicktime plug-in control box doesn't respond

Categories

(Core Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 108835

People

(Reporter: riscky, Assigned: peterlubczynski-bugs)

References

()

Details

Plug-in doesn't respond to plug-in control options

- Play any QT movie (i suggest from the trailers so you can work and have fun at
the same time)
- While movie is playing, played or loading press the control option (down arrow
on bottom right of plug-in)
- Select 'About Quick Time Plug-in..."
- Nothing happens (a window should appear that tells about the quicktime plug-in_

- Next select 'Plug-In Settings..."
- Nothing happens (the System Preferences should load and to the QuickTime
preference panel)

All Plug-In options fail. This may be related to bug 110190

Using Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.5+) Gecko/20011115
Build ID 2001111506
-->peterl
Assignee: av → peterlubczynski
FWIW, this WorksForMe using Fizzilla/2001101516 (0.9.5).
After Greg's post I tried this under .9.5 and it works... still a no go in the
latest trunk
I just used QT 5.0.2.15 in 2001-11-16-03 watching the Star Wars Episode II
trailer today.. http://starwars.apple.com/ep2/forbidden/forbiddenlove_sm.html
and works for me, didn't try 5.0.2 before I downloaded the new 5.0.2.15
(plugins' properties version page info)  QT 5.0.1 crashes or has problems.. try
a new QT download.

also see bug 110564, bug 110528, and bug 110441
I have a screenshot of it working on W2K with QT version 5.0.2.15.  and today's
trunk 11-16.  
so if its not QT's fault, then its platform related.
This problem is a regression with the Mac OS X build.
Status: UNCONFIRMED → NEW
Ever confirmed: true

*** This bug has been marked as a duplicate of 108835 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v d
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.