Bug 475187 - Small modifications to totem mozilla plugin to enable it to work in OpenOffice.org
Small modifications to totem mozilla plugin to enable it to work in OpenOffic...
Product: Fedora
Classification: Fedora
Component: totem (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-08 07:49 EST by Caolan McNamara
Modified: 2009-03-04 14:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-04 14:20:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to do this (3.64 KB, patch)
2008-12-08 07:49 EST, Caolan McNamara
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 563826 None None None Never

  None (edit)
Description Caolan McNamara 2008-12-08 07:49:59 EST
Created attachment 326127 [details]
patch to do this

Description of problem:
OOo has a little feature to support embedded mozilla plugins inside OOo which we're gotten working again. The target plugin is typically the adobe flash plugin. Some very small mods to the totem plugin make it suitable for working the api that OOo supports.

oowriter->Insert->Object->Video-> And use a .ogg would work in rawhide OOo openoffice.org-core-3.0.1-12.3.fc11.1

a) Don't consider not getting a mBaseURI if we can't get what we need as fatal
b) A height of -1 is still "max" height as the comment somewhere else in that .c says
c) And allow a smaller mozilla vtable than the one we build against if its big enough to support what we use
Comment 1 Bastien Nocera 2008-12-08 11:32:03 EST
Could you please push the patch upstream?

Makes it easier to review, and I'd like to have comments from Christian Persch about it.
Comment 2 Bastien Nocera 2009-03-04 14:20:16 EST
Already handled upstream.

Note You need to log in before you can comment on or make changes to this bug.