Closed GoogleCodeExporter closed 9 years ago
This is working as designed, firefox gives us a window to draw to and we use
the size
of the window.
Original comment by kdeko...@gmail.com
on 30 Jan 2010 at 1:58
Is there any way to add an option to display in the native size? Or is that a
bug I
need to file with Firefox? The mplayerplug-in did show it in native size when
a size
wasn't explicitly specified, and gecko-mediaplayer is a superior product in
terms of
stability and user-interface, which is why I was hoping it would be possible...
Is this something I should take up with Firefox, or would it be possible to add
a
user-configurable option to "obey native size" rather than "obey Firefox" ?
Thanks!
Original comment by aca...@gmail.com
on 30 Jan 2010 at 2:14
Are there any mplayer flags we can pass for this to work correctly? This defect
is a showstopper in my books and has forced me to still use mplayerplug-in,
which scales properly.
I can tell firefox to directly launch non-embedded media in separate mplayer
windows, but would rather have multiple tabs of media.
Original comment by microwav...@gmail.com
on 17 Mar 2011 at 4:29
I guess I don't understand your problem. I loaded up a 16:9 video in my browser
and it scaled completely correctly. Notice the black bars around the image, and
it filling the window to the left and right. The original size of this image is
480x210 and as you can see the browser window is much larger.
Or what you want is no scaling of the image, and you want it the native size of
the image?
Original comment by kdeko...@gmail.com
on 17 Mar 2011 at 4:37
Attachments:
Ok I think I understand what you want. I just committed a change to SVN to
disable video scaling when embedded. There is a preference to do this in the
plugin tab. Check 'disable embedded player scaling' and it will leave the image
in the original size.
You will want gecko-mediaplayer and gnome-mplayer both from SVN for this to
work.
If you have any issues with this please open a new issue as this bug is closed.
Original comment by kdeko...@gmail.com
on 17 Mar 2011 at 5:03
Original issue reported on code.google.com by
aca...@gmail.com
on 30 Jan 2010 at 1:23