Closed Bug 327680 Opened 20 years ago Closed 20 years ago

Realplayer doesn't work smoothly in Camino 1.0 and causes trouble

Categories

(Camino Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: w.a.schmidt, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 (MultiLang) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 (MultiLang) Realplayer doesn't work smoothly in Camino 1.0. See, e.g., http://www.br-online.de/alpha/centauri/. Video is dropping and hanging. (No problems with Safari or Firefox!) After clicking on a button in the realplayer, other objects on the page get selected when the mouse is moved. When switching to another tab, the Realplayer window will show up there. OS is MacOS X 10.4.5. Realplayer is "RealPlayer 10 für Mac OS X". Reproducible: Always Steps to Reproduce: 1. open a new tab 2. load the above URL 3. try to watch the movie for a while 4. stop the movie 5. move the mouse 6. go back to previous tab
I see the jerkiness -- it's not too bad, but it's definitely worse than in Safari -- with 1.0. This may be a dupe of existing performance issues. The bleed-through is covered in other bugs. Leaving UNCO for now. cl
See also bug 322850. The click-in-plugin-and-then-page-gets-selected is filed, too (two bugs), but I can't find them right now. Bleed-through is bug 156583.
Is this still an issue with 1.0.1 or a recent nightly and 10.1.0 (v412)?
Assignee: mikepinkerton → nobody
QA Contact: plugins
This is greatly improved on the trunk following the threads landing...not perfectly smooth, but still very good on my crappy connection. The extensive threads changes won't be backported, so closing "WFM on the trunk."
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.