Closed Bug 185936 Opened 23 years ago Closed 4 years ago

Website does not detect WildTangent GameChannel when loading program

Categories

(Core Graveyard :: Plug-ins, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: blackstarseed, Assigned: peterl-bugs)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 When I click on the "Play game" button in Mozilla, two windows pop up, one being the actual program, a second stating that the latest update of the WildTangent Game Channel needs to be installed, when it already has been installed. This does not happen elsewhere. Reproducible: Always Steps to Reproduce: 1. Click on the Play Game button. 2. 3. Actual Results: The two windows pop up, one being the actual program, the other stating that WildTangent needs to be updated. Expected Results: Mozilla should have not had a window stating that WildTangent Game Channel needs to be updated, when it already has. The plugin is WildTangent GameChannel Web Driver v. 1.5.
reassign
Assignee: beppe → peterl
The page is trying to start a plugin for 'application/x-wildtangent-host'. Is this mime type listed in about:plugins? If not, try to locate the plugin DLL and copy it to your plugins folder. It will likely start with 'np'. You can get more debug information by running with: set NSPR_LOG_MODULES=Plugin:8,PluginNPN:8,PluginNPP:8,nsHTTP:5 and set NSPR_LOG_FILE=c:\log.txt
--->future WildTanget is not teir1 plugin vendor. Please ensure you have the NP*.DLL in your plugins folder.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
QA Contact: shrir → bmartin
Target Milestone: --- → Future
WildTangent plugin DLL is npwtplug.dll. Find that file.
QA Contact: bmartin → plugins
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.