"Live365 - Player Window" gives a javascript error which prevents music from playing

RESOLVED EXPIRED

Status

()

Core
Plug-ins
RESOLVED EXPIRED
14 years ago
7 years ago

People

(Reporter: env, Unassigned)

Tracking

({helpwanted})

Trunk
x86
Windows XP
helpwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Live365 hosts internet radio stations. The "Live365 - Player Window" is 
responsible for playing a station.  There is a JavaScript error in the player 
window that prevents the media player from activating.  The JavaScript error 
is "document.PlayerControl.GetPlayState is not a function"

Reproducible: Always
Steps to Reproduce:
1. Go to live365.com
2. Play a station.
3. When the Player Window loads, the JavaScript error will occur and no music 
will play.

Actual Results:  
The JavaScript error is "document.PlayerControl.GetPlayState is not a 
function" occurs and no music is played.

Expected Results:  
Loaded a media player and played music.

Comment 1

14 years ago

*** This bug has been marked as a duplicate of 53532 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
Bill Mason, why did you mark this a dup of bug 53532?  The two bugs have
different test URLs, different test procedures, different expected and actual
results....

/be
Status: RESOLVED → UNCONFIRMED
Component: JavaScript Engine → Plug-ins
Resolution: DUPLICATE → ---

Comment 3

14 years ago
Duplicate or related to bug 56532 ?
Active X plugin?  I'll let someone else mark this a dup of bug 56532.  Bill
Mason clearly meant to dup it against that bug and just typo'd 6 as 3 -- he
should feel free to re-dup.

/be

Comment 5

14 years ago
I don't think this is related to 56532. I have the same problem. Note that this
was not a problem until I upgraded to 1.6. Live365 worked just fine under 1.5.
It remains a problem under 1.7b.

Note that the error described occurs when the RealPlayer option in Live365 is
selected. When MP3 is selected, which runs Winamp, I get a different behavior,
where the Javascript error does not occur, Winamp starts, but does not have a
connection to the server and does not play.

It works just fine under Internet Explorer. (Complete with popunder ads, ick.)

Updated

14 years ago
Keywords: helpwanted
bclary, any insights?

/be

Comment 7

14 years ago
*** Bug 263417 has been marked as a duplicate of this bug. ***
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/
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
Last Resolved: 14 years ago13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.