Closed
Bug 252413
Opened 20 years ago
Closed 19 years ago
Webradio component not working
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: sigma, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
The webradio component at www.vinyl107.se isn't able to play any content when
using Firefox. The window comes up, but nothing happens when I choose one of the
radio channels.
Reproducible: Always
Steps to Reproduce:
1. Enter www.vinyl107.se
2. Click the "lyssna live" button
3. Click on any of the radio channels in the list to the right. The selected
channel should start playing, it doesn't.
Actual Results:
Nothing.
Expected Results:
The channel should have started playing and the main window should have been
updated to include more information on the current channel.
Comment 1•20 years ago
|
||
Error: document.all has no properties
Source File: http://www.nwrweb.com/player/show/vinyl107/vinyl107/20
Line: 395
Error: currentPlugin has no properties
Source File: http://www.nwrweb.com/player/show/vinyl107/vinyl107/20
Line: 455
Comment 2•20 years ago
|
||
Duplicate of bugid: 121832 ??
WMP is not scriptable from Geko based browsers. RESOLVED/WONTFIX
<http://bugzilla.mozilla.org/show_bug.cgi?id=121832>
Possible workaround is to use the active-x plugin support for Mozilla found at:
<http://www.iol.ie/~locka/mozilla/plugin.htm>
"IMPORTANT! Only download the plugins for the correct browser version. Don't
bother downloading the plugin if it does not match your browser version - it
will crash or do nothing. If you ignore this advice and discover your browser
now crashes every time a page contains an ActiveX control, delete npmozax.dll
from your plugins\ dir to fix it"
Also note security problems that come with ActiveX
JdG
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•