forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
pepper: Use the RenderThread's shared context as the parent context.
Remove the PepperParentContextProvider interface entirely. Have the pepper PlatformContext3DImpl go directly to RenderThreadImpl and get the offscreen shared context, and create its texture with that context and make it the parent of the PlatformContext3DImpl context3d. Remove the SetParentContext() method from the PlatformContext3DImpl and the plugin delegate, and the fullscreen widget. Instead, when the plugin delegate or fullscreen widget become active, in ReparentContext() they have the PlatformContext3DImpl require access to the offscreen shared context and create the parent texture id with it, if needed. The fullscreen widget context management needs to be adjusted. Previously PlatformContext3DImpl would call back into the fullscreen widget which would create the fullscreen widget's context. But we have removed that circular trip. Now in RenderWidgetFullscreenPepper::CheckCompositing() if compositing mode is being used, we create the fullscreen context3d. We also recreate it if the old context was lost. When leaving compositing mode, the fullscreen widget's context is destroyed. The fullscreen widget's context is now made to share resources so that it can access the texture created by the RenderThread's context. This fixes the known issue where fullscreen remains black after a context loss. R=piman BUG=181052 Review URL: https://chromiumcodereview.appspot.com/12673002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187109 0039d316-1c4b-4281-b951-d872f2087c98
- Loading branch information
danakj@chromium.org
committed
Mar 9, 2013
1 parent
bb4f11b
commit a44c1b2
Showing
9 changed files
with
76 additions
and
164 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.