Closed Bug 349065 Opened 18 years ago Closed 18 years ago

Some Videos on CNN.com falsely display Windows Media not Detected Message

Categories

(Core Graveyard :: Plug-ins, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: steve_d, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 With Windows Media Player (tried with both version 10 and 11) apparently correctly installed and working with Internet Explorer, attempts to view some of the videos on CNN (not all of them) using Firefox result consistently in a "Windows Media Not Detected" message. The problem seems connected with an incompatibility when either Adblock or Adblock Plus are installed. Reproducible: Always Steps to Reproduce: 1. With Adblock or Adblock plus installed, start Firefox 2. go to http://www.cnn.com 3. Click on one of the links usually labeled "Watch Video" in center of page. Actual Results: Screen comes up saying "Plugin Warning / No Windows Media Player Detected" with link for installing the player. Attempting the installation results in the same message. Expected Results: The video was expected to display. IE in contrast stalls slightly but then loads and runs the video using the Windows Media Player. Uninstalling AdBlock or Adblock Plus allows the video to display in Firefox, at the price of not having ad blocking available. Reinstalling Adblock or Adblock Plus - even when not enabled or when the list of filters is empty - re-introduces the problem.
This could very well be an Adblock bug.
Component: Preferences → Plug-ins
Product: Firefox → Core
QA Contact: preferences → plugins
Version: unspecified → 1.8 Branch
I now finally retried Firefox reinstall one more time, more completely than before including by manually deleting leftover Mozilla directories after using Add/Remove and deleting obvious leftover registry keys, after rollback to Media Player 10 (including uninstalling Windows Media Format 11 Runtime and then uninstalling Microsoft User-Mode Driver Frameworks Feature Pack 1.0, as per Media Player FAQ on Microsoft support site). That appears to have cured the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
No specific bug / patch referenced as the fix. -> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.