summaryrefslogtreecommitdiffstats
path: root/webkit/glue/plugins/pepper_private2.h
Commit message (Collapse)AuthorAgeFilesLines
* Move the Pepper implementation from webkit/glue/plugins/pepper_* tobrettw@chromium.org2010-12-161-42/+0
| | | | | | | | | | | webkit/plugins/ppapi/*. This renamed the files and interface implementation classes from foo.cc/Foo to ppb_foo_impl/PPB_Foo_Impl to match the proxy ppb_foo_proxy/PPB_Foo_Proxy. This moves plugin_switches.* from webkit/glue/plugins to webkit/plugins. Review URL: http://codereview.chromium.org/5828003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69424 0039d316-1c4b-4281-b951-d872f2087c98
* Make the DrawGlyphs call have the proper const arguments, and make the proxiedbrettw@chromium.org2010-12-021-3/+3
| | | | | | | | | | | version of this API synchronous. Otherwise, the caller may end up trying to draw over the text that isn't there yet. TEST=none BUG=none Review URL: http://codereview.chromium.org/5555004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68108 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps. This is a re-land ↵brettw@chromium.org2010-11-021-2/+2
| | | | | | from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64757 0039d316-1c4b-4281-b951-d872f2087c98
* Revert PPAPI change due to Linux compile failures.brettw@chromium.org2010-11-021-2/+2
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64751 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps.brettw@chromium.org2010-11-021-2/+2
| | | | | | | | | This is a re-land from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64750 0039d316-1c4b-4281-b951-d872f2087c98
* Revert PPAPI change.brettw@chromium.org2010-11-021-2/+2
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64719 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps.brettw@chromium.org2010-11-021-2/+2
| | | | | | | | | This is a re-land from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64718 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 64716 - Switch to the new PPAPI repository. This removes the DEPS ↵brettw@chromium.org2010-11-021-2/+2
| | | | | | | | | | | | | | entry that refers to the PPAPI repo, and fixes the includes to use the new location. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/4164015 TBR=brettw@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64717 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to the new PPAPI repository. This removes the DEPS entry that refers tobrettw@chromium.org2010-11-021-2/+2
| | | | | | | | | | the PPAPI repo, and fixes the includes to use the new location. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/4164015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64716 0039d316-1c4b-4281-b951-d872f2087c98
* Add a glyph drawing routine to private Pepper interface. The currentbrettw@chromium.org2010-10-081-0/+19
| | | | | | | | | | | | | | | implementation is Linux only. This also changes the Private font interface to use the "regular" PP_FontDescription_Dev struct for specifying the font, which allows us to unify some of the data here. I kept the character set stuff as a separate parameter which is needed for compat in a few cases. TEST=none BUG=none Review URL: http://codereview.chromium.org/3569013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61920 0039d316-1c4b-4281-b951-d872f2087c98
* Add some optimizations to plugin painting.brettw@chromium.org2010-09-241-0/+23
| | | | | | | | | | | | | | | | | | The simplest one is to disable blending when the plugin is opaque. The more complicated one is to bypass webkit painting the background of plugins when we know the plugin to be always on top and also opaque. The always on top flag is currently set by a new "Private2" API. Bypassing WebKit makes animations faster. This is a re-land of the previous patch with a trivial compilation fix. This also adds a clip rect to the GetBitmap... function so we can properly handle plugins in nested iframes with proper clipping. BUG=none TEST=none Original review URL: http://codereview.chromium.org/3421030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60426 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Add some optimizations to plugin painting."maruel@chromium.org2010-09-231-23/+0
| | | | | | | | | | | | This reverts commit 60329. TBR=brettw BUG= TEST= Review URL: http://codereview.chromium.org/3442013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60331 0039d316-1c4b-4281-b951-d872f2087c98
* Add some optimizations to plugin painting.brettw@chromium.org2010-09-231-0/+23
The simplest one is to disable blending when the plugin is opaque. The more complicated one is to bypass webkit painting the background of plugins when we know the plugin to be always on top and also opaque. The always on top flag is currently set by a new "Private2" API. Bypassing WebKit makes animations faster. BUG=none TEST=none Review URL: http://codereview.chromium.org/3421030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60329 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-01 02:52:27 +0000