Closed Bug 358944 Opened 18 years ago Closed 17 years ago

WMP11 videos resize incorrectly when scaled

Categories

(Firefox :: File Handling, defect)

2.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: travisowens, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 While this worked fine with WMP10, but I install WMP11 (final) today and viewed a page where I had a .WMV video encoded at 320x240 but the HTML shows the video at 640x480. Upon viewing the video, the window initially draws at 640x480 then instantly resized down to 640x240. <object width="640" height="480" type="video/x-ms-wmv" data="Unity_Family.wmv"> <param name="autostart" value="true" /> <param name="controller" value="true" /> <param name="src" value="Unity_Family.wmv"> </object> Reproducible: Always Steps to Reproduce: 1. Get a WMV video 2. Put it in a webpage and double the viewing resolution
Version: unspecified → 2.0 Branch
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 07/14
Yes, I still see this bug in 2.0.0.4
Does comment 3 fix your issue reporter? If so, please mark this bug as WORKSFORME. Thanks!
This plugin improves the behavior by playing the video with the correct aspect ratio, but it plays the video in it's original ratio, and not the resolution provided in the HTML markup. As a user I have to manually set a zoom level in the WMP UI, which is not the intention of the web author. Despite this fact, mixed with the point that this bug is mostly a cosmetic issue that's now 9 months old makes it trivial and I'm therefore going to reluctantly mark this bug as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Whiteboard: CLOSEME 07/14 → WORKSFORME 7/26
Whiteboard: WORKSFORME 7/26
You need to log in before you can comment on or make changes to this bug.