| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For the shared stuff we have a ppapi/shared_impl/VarTracker and a
ppapi/shared_impl/ResourceTracker. The host side of the proxy inherits
HostResourceTracker from ResourceTracker and then adds a bunch of var tracking
stuff to that, which makes no sense.
This moves the var tracking stuff out into a separate HostVarTracker so that's
all in one object. The host version just adds the NPObject tracking on top of
the shared VarTracking.
BUG=
TEST=
Review URL: http://codereview.chromium.org/8322017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106593 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the confusion that comes from there being two:
webkit/plugins/ppapi/resource_tracker and
ppapi/shared_impl/resource_tracker.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/8320010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106588 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ Reland of 106142: http://codereview.chromium.org/8316008 ]
This adds a specialization on the host and plugin side of the proxy. This
replaces the ad-hoc singleton tracking done by the resource and var trackers
with just being getters on this global object.
Most code can use the single PpapiGlobals class. I also allow code to get the
host and plugin specializations since some code needs access to some specific
features of each side.
In a later pass I'll move the other stuff out of TrackerBase and delete it.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/8344025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106537 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=96318
TEST=
Review URL: http://codereview.chromium.org/8275012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106521 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
- removing unused methods
- making some remaining cleanups
BUG=none
TEST=green bots
Review URL: http://codereview.chromium.org/8231004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106242 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=95805
TEST=unittests of touched files pass, manually tested w/ sonyh2.webm which is >5G (internal only), and trybots.
Review URL: http://codereview.chromium.org/8349009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106183 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a specialization on the host and plugin side of the proxy. This
replaces the ad-hoc singleton tracking done by the resource and var trackers
with just being getters on this global object.
Most code can use the single PpapiGlobals class. I also allow code to get the
host and plugin specializations since some code needs access to some specific
features of each side.
In a later pass I'll move the other stuff out of TrackerBase and delete it.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/8316008
TBR=brettw@chromium.org
Review URL: http://codereview.chromium.org/8342016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106148 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a specialization on the host and plugin side of the proxy. This
replaces the ad-hoc singleton tracking done by the resource and var trackers
with just being getters on this global object.
Most code can use the single PpapiGlobals class. I also allow code to get the
host and plugin specializations since some code needs access to some specific
features of each side.
In a later pass I'll move the other stuff out of TrackerBase and delete it.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/8316008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106142 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It actually returns true or false depending on whether or not the plugin
handled the event. Treating as an NPError is just asserting that the
plugin claimed not to handle the event. Ignore the return value instead.
BUG=none
TEST=Flash still works, plugins which do return true (npapi-sdk sample plugin) don't trigger a DCHECK
Review URL: http://codereview.chromium.org/8216033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106126 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8342004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106116 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=100640
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8319021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105948 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8318025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105925 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8321014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105912 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8294015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105905 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
R=csilv@chromium.org
Review URL: http://codereview.chromium.org/8315012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105888 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=41781
TEST=None
Review URL: http://codereview.chromium.org/8295023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105707 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=41780
TEST=in CL
Review URL: http://codereview.chromium.org/8291002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105590 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FlashFullscreen.
Tested with ppapi/native_client/tests/ppapi_browser/ppb_fullscreen
upgraded with 2D graphics. Will commit in a separate patch.
BUG=41780
TEST=ppapi/tests/test_fullscreen + see above
Review URL: http://codereview.chromium.org/8275031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105530 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=67091, 92045, 92218
TEST=NONE
Review URL: http://codereview.chromium.org/8051018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105520 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and if the current element is the fullscreen element. This will help us
determine more reliably if the plugin entered/exited fullscreen mode. This
also takes care of the F11 case where desired_fullscree_state_ has not been
properly set.
Add an dummy stub for RenderWidget::is_fullscreen to be implemented
by darin in a different patch) and wrappers for it to make it available
via PluginDelegate::IsInFullscreenMode to the PluginInstance.
BUG=41780,98477
TEST=ppapi_tests/test_fullscreen, native_client/tests/ppapi_browser/ppb_fullscreen
Review URL: http://codereview.chromium.org/8273029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105485 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to fill in the screen in SetFullscreen. Reset plugin size in ViewChanged when we exit. Update tests.
We are forced to resize the plugin in the Pepper layer because WebKit does yet do it.
It only moves the plugin to the middle of the screen with the expectations the
web page will contain the following css:
:-webkit-full-screen {
width: 100%; height: 100%;
}
That's not acceptable for Pepper/NaCl users.
BUG=41780,98474
TEST=in CL
Review URL: http://codereview.chromium.org/8228023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105476 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
BUG=99557
Review URL: http://codereview.chromium.org/8275003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105414 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change Chrome to allocate most OpenGL contexts with the
kCGLPFAAllowOfflineRenderers flag, and specify
NSSupportsAutomaticGraphicsSwitching in the Info.plist for the main
executable and helper apps. This keeps Chrome on the integrated GPU
except when using WebGL, accelerated 2D Canvas, Pepper 3D, and Core
Animation-based plugins (except Flash).
Chrome shares resources between OpenGL contexts in order to display WebGL
and other content in the compositor, and resource sharing doesn't work
between contexts allocated on different GPUs. Therefore, when the first
context for a given renderer requests the discrete GPU, the channel is
dropped and all contexts are reallocated on the discrete GPU. Similarly,
when the last context requesting the discrete GPU for a given renderer is
shut down, all contexts are dropped and reallocated on the integrated GPU.
Currently dynamic GPU switching is only supported on the latest Mac OS X
10.7 update and MacBook Pros with dual AMD / Intel GPUs, though this will
improve in future OS updates.
Tested with WebGL, CSS 3D, Flash and Unity3D content and observed desired
GPU switching behavior. Also added a layout test to WebKit under
https://bugs.webkit.org/show_bug.cgi?id=69776 which when run in Chrome
catches an assertion failure related to the destruction of contexts. The
intent is to add it as a UI layout test on the GPU bots.
BUG=88788
TEST=none
Review URL: http://codereview.chromium.org/8233027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105399 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
dialog when thesuggested file name is a root directory, such as "C:\".
BUG=73070
TEST=manual
Review URL: http://codereview.chromium.org/8142018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105247 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, we end up picking the wrong visual and confusing things like
plugins.
BUG=21253
TEST=run Xephyr :1 -screen 800x600 -screen 800x600, run chrome on DISPLAY=:1.1; nspluginwrapper should work, flash shouldn't complain in gdk_x11_colormap_foreign_new
Review URL: http://codereview.chromium.org/8221031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105236 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=99011
TEST=Please refer to bug report.
Review URL: http://codereview.chromium.org/8231030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105167 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves all browser-side synchronous callers to use the asynchronous
PluginService interface.
BUG=17863,95114
TEST=Covered by tests. Plugins still work.
Review URL: http://codereview.chromium.org/8071013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105069 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=59425
TEST=Build chrome and ppapi_example_ime,
Confirm "out/Release/chrome --register-pepper-plugins='out/Release/lib/libppapi_example_ime.so;application/x-ppapi-example' ppapi/examples/ime/ime.html" works.
This CL is the last part for adding the basic IME support for PPAPI,
preceded by the previous two changes
codereview.chromium.org/7882004 (API declarations) and
codereview.chromium.org/7978019 (thunk and proxy implementation).
This CL comes with the actual Chrome-side implementation of the API
with an example to show how to use IME in PPAPI.
Keep in mind the current implementation still not reached the point of "the complete" set of IME APIs yet.
- Advanced features in design doc (like surrounding text retrieval) is not available.
- DOM and PPAPI composition events are not converted each other.
Rather, it aims to provide basic set of functions just needed to implement inline composition in plugins.
Review URL: http://codereview.chromium.org/8073021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105056 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This removes a bunch of plumbing for the proxy and impl sides, and uses the
new macro system for registering the interface. This saves a lot of code and
a bunch of boilerplate files could be deleted.
Review URL: http://codereview.chromium.org/8159003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104850 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes us not hold a ref to the PluginModule during sending async messages.
Previously we would cancel callbacks in the PluginModule destructor and this
would change the ref count from 0 to 1, and then back to 0, calling reentrantly
into the destructor again.
Not holding a ref during async messages prevent this problem. I also added
some checking to detect sync messages during shutdown, and also reentrant
destructors should this happen again.
BUG = http://crosbug.com/21258, http://crbug.com/99398
Review URL: http://codereview.chromium.org/8222021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104847 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
This removes some duplicate code between the proxy and the impl.
Review URL: http://codereview.chromium.org/8159012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104741 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
crash.
BUG=NONE
TEST=1. goes to http://www.vimeo.com/hd
2. play any video and enter fullscreen mode.
3. right click to open Flash context menu.
4. choose Global Settings..., which causes the browser window to be brought to the foreground.
5. close the tab of http://www.vimeo.com/hd
6. the settings page should not crash.
Review URL: http://codereview.chromium.org/8198013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104693 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the next input event.
BUG=94981
TEST= 1) run manual test in ppapi/example;
2) click on the plugin;
3) the cursor should change to a rectangle and keep changing its dimensions, even if you don't move/click the mouse.
Review URL: http://codereview.chromium.org/8196003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104686 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
change. To make chrome not know about PepperPluginDelegateImpl and to remove a duplicated block of code, I've modified the plugin creation code a little in content. This also makes WebPlugin creation simpler since it doesn't get the mime type in two ways and has to know to ignore the one in the struct.
BUG=98716
Review URL: http://codereview.chromium.org/8200019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104624 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=35223
TEST=ppapi ui_tests
Review URL: http://codereview.chromium.org/8135010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104572 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
I revved the PPP_VideoDecoder interface since IDL wants to pass PP_Picture_Dev
by pointer instead of by value. This also renames the VIDEO_CAPTURE interface
string/define to VIDEOCAPTURE for consistency (what IDL wants to do).
Review URL: http://codereview.chromium.org/8144008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104569 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
r=darin
BUG=99395
Review URL: http://codereview.chromium.org/8189001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104494 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8174005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104382 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
channel.
Review URL: http://codereview.chromium.org/8146004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104371 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104103 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This change adds a new class WebPluginIMEWin that converts the platform-independent IME data sent from a renderer process (or WebKit) to the Win32 IME messages and send them to a plug-in. To allow the plug-in to retrieve the IME data with IMM32 function calls, this change also adds a patch to GetProcessAddress(). (Flash seems to retrieve the pointers to IMM32 function with this function.) This change also sends IME status retrieved from the plug-in to a browser process (via a renderer process).
BUG=82507
TEST=manual
Review URL: http://codereview.chromium.org/7082034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103869 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
forcing a full
frame invalidation on scroll offset changes. Current Pepper2D plugin
scrolling is fundamentally incompatible with how pages scroll in the accelerated compositing. Plugins rely on
shifting the existing backing and backfilling whereas the compositor scrolls by moving the viewport on top
of a fixed document.
BUG=chromium-os:18521
Review URL: http://codereview.chromium.org/8100017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103831 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=95650
TEST=start about:tracing and run nacl app, verify that input and paint trace events show up.
Review URL: http://codereview.chromium.org/8113010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103829 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
one is already pending.
It is not clear what one should expect. Should the 2nd request override the 1st one?
Should it be queued up and processed as if it was placed after the 1st one finished?
Should it be ignored? In reality, the 2nd transitions does not occur while still
messing up the state of 1st one (e.g. the window goes into fullscreen, but fullscreen
DidChangeView never fires). Even with the JS interface, the behavior appears to be
broken: http://www/~polina/fullscreen.html. Since the feature is not particularly useful,
it is cleanest to just deny it in Pepper.
BUG=41780
TEST=in CL
Review URL: http://codereview.chromium.org/8093013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103767 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename CompletionCallback to OldCompletionCallback in preparation for introducing a new CompletionCallback based on base::Callback.
Also renames other CompletionCallback types like CancelableCompletionCallback and TestCompletionCallback and CompletionCallbackImpl. All using sed with s/CompletionCallback/OldCompletionCallback/g.
BUG=98719
TEST=none
Review URL: http://codereview.chromium.org/8070013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103650 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Refuse to lock the mouse if the security origin of the document containing the requesting pepper plugin cannot access the security origin of the main frame document.
BUG=41781
TEST=None
Review URL: http://codereview.chromium.org/8070011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103607 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome/src/webkit/plugins/npapi/webplugin_delegate_impl.h.
BUG=97131
TEST=none
Review URL: http://codereview.chromium.org/8100006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103592 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to the underlying plugin
object getting destroyed in the context of an incoming ExecuteScript call while the renderer is waiting
for an javascript function call on the plugin object to return.
We need to grab a reference on the plugin module in the dispatcher code and in the plugin object as
there are two crashes which occur here
1. When the dispatcher send is about to return from the Send call and it tries to unmarshal the return
values.
2. The other crash is in the wrapper class Invoke function where we crash similarly.
Fixes bug http://code.google.com/p/flapper/issues/detail?id=77
Review URL: http://codereview.chromium.org/8098001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103570 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=98514
TEST=PluginListTest.*
Review URL: http://codereview.chromium.org/8070024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103318 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=59425
TEST=Check that ppapi_tests compile (with GYP_DEFINES=shared_library, too).
This CL is the second (out of three) part for adding IME support for PPAPI.
It reflects comments from James Su to the previous CL:
http://codereview.chromium.org/7882004.
- Renamed ..._COMPOSTION_START to _IME_COMPOSITON_START.
- Changed to assure GetSegment to return a strictly increasing sequence of
segmentation points from 0 to the length.
and,
- Added the mostly boilerplate code for interfacing with
in-process & out-of-process plugins.
The actual implementation of the IME support will come as
the next and the last part of this series of patches.
Review URL: http://codereview.chromium.org/8059006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103234 0039d316-1c4b-4281-b951-d872f2087c98
|