http://dev.w3.org/2011/webrtc/editor/webrtc.html - Some of the functions are are overriden by the proposal in https://docs.google.com/a/google.com/document/d/1nfA1ElWed5PPR4nqenEkxNMMLRfzAsh1yMLe8yRcns8/edit#
The implementation is in rtc_peer_connection_handler.cc and is called RTCPeerConnectionHandler. It implements the new WebKit interface WebKit::WebRTCPeerConnectionHandler.
The idea is to keep the previous PeerConnection version around until web developers have had time to upgrade to the new API. The Chrome glue code for the old version is in peer_connection_handler_jsep.cc.
The implementation is called PeerConnectionHandlerJsep and implements WebKit::WebPeerConnection00Handler
BUG=142829
TEST= Tested with the included unit test. A PyAutoTest is also beeing uploaded for review.
Review URL: https://chromiumcodereview.appspot.com/10703095
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156608 0039d316-1c4b-4281-b951-d872f2087c98
This is a proposed solution for the problem with using WebFrame* web_frame = WebFrame::frameForCurrentContext() in
renderer_webkitplatformsupport_impl.cc
https://chromiumcodereview.appspot.com/10703095/diff/13017/content/renderer/renderer_webkitplatformsupport_impl.cc
This should be seen as step 1 in refactoring how PeerConnections are created and used. If PeerConnections should be created in the RenderThreadImpl - so should all objects that it is dependent on such as the P2PSocketDispatcher that is currently created and owned by the RenderViewImpl.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10919122
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156515 0039d316-1c4b-4281-b951-d872f2087c98
This change integrates the Hyphenator class to content so Chrome can use it. This change basically consists of two parts:
* Adds a couple of IPC messages so a renderer asks a browser to open hyphenation dictionaries;
* Adds a HyphenatorMessageFilter class, which opens hyphenation dictionaries in a browser process;
* Changes the Hyphenator class to send IPC messages to open hyphenation dictionaries.
BUG=47083
TEST=HyphenatorTest.SetDictionary,HyphenatorMessageFilterTest.OpenDictionary
Review URL: https://chromiumcodereview.appspot.com/10854245
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154663 0039d316-1c4b-4281-b951-d872f2087c98
BUG=none
Test=Some new browser plugin tests that will be upstreamed independently
Review URL: https://chromiumcodereview.appspot.com/10823086
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149297 0039d316-1c4b-4281-b951-d872f2087c98
This CL does the following:
* Move AudioDevice, AudioInputDevice out of content, into media/audio.
* ...and a couple of dependent classes: AudioDeviceThread and ScopedLoopObserver.
* ...and the unit test.
* Renamed AudioDevice -> AudioOutputDevice
* Moved the classes into the media namespace.
* Updated the unit test code as necessary.
Aside from the unit test*, there are minimal code changes. Only what was required to make things build and work as before - mostly just adding or removing "media::".
* The unit test changes were to add expectations for AddDelegate/RemoveDelegate since previously a mock class was inheriting from AudioMessageFilter and not the IPC interface.
Review URL: https://chromiumcodereview.appspot.com/10834033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148777 0039d316-1c4b-4281-b951-d872f2087c98
Note that JSEP 00 is still supported and we are adding support for JSEP01.
TEST= Run content unit tests and ./chrome/test/functional/webrtc_call.py
apprtc.appspot.com is also a nice page to try out. Start chrome with the enable-peer-connection flag.
Review URL: https://chromiumcodereview.appspot.com/10804004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148548 0039d316-1c4b-4281-b951-d872f2087c98
The problem is that RenderViewFakeResourcesTest creates a RenderThreadImpl, but without setting up the sandbox environment, specifically the domain socket used on Linux. This caused the sandbox's pre-assigned file descriptor to be taken by other files or sockets, leading to a hang when the sandbox code tries to talk to the browser.
To fix this, add a way for tests to disable the WebSandboxSupport implementation in RendererWebKitPlatformSupportImpl.
The problem also affects WebRTCAudioDeviceTest, so fixed it there as well.
BUG=128705
Review URL: https://chromiumcodereview.appspot.com/10449094
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140631 0039d316-1c4b-4281-b951-d872f2087c98
as they are no longer used in WebKit.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10453037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139542 0039d316-1c4b-4281-b951-d872f2087c98
Corresponding webkit change: https://bugs.webkit.org/show_bug.cgi?id=86995
The plan includes eventually deprecating two separate IPC calls
GetFileSize() and GetFileModificationTime() in favor of GetFileInfo().
BUG=none
TEST=existing tests should pass
Review URL: https://chromiumcodereview.appspot.com/10441016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139022 0039d316-1c4b-4281-b951-d872f2087c98
DomStorageDispatcher class, and move existing renderer side domstorage
sources into a subdirectory so OWNERS can be applied more meaningfully.
BUG=94382
TBR=jam
Review URL: https://chromiumcodereview.appspot.com/10162015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136188 0039d316-1c4b-4281-b951-d872f2087c98
events into webkit/webcore. This also includes informing DomStorageContext
EventObservers of session storage mutations too since we're switching to handling
them in the same way as local storage events.
Note: This is patch 2 of a multi-sided affair. The new event handling won't be fully
turned on until patch 3 on the webkit side. Here's patch 1...
https://bugs.webkit.org/show_bug.cgi?id=84387
BUG=94382
Review URL: https://chromiumcodereview.appspot.com/10201010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134037 0039d316-1c4b-4281-b951-d872f2087c98
- delete old in_process_webkit sources (hooray)
- rename the new sources to no longer have the _new suffix
- fix up the includes
- remove the ENABLE_NEW_DOM_STORAGE_BACKEND flag since old stuff is now gone
Review URL: https://chromiumcodereview.appspot.com/10086018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132504 0039d316-1c4b-4281-b951-d872f2087c98
This adds glue for JSEP PeerConnection. PeerConnectionHandler is split in two classes and a base class. The class name is kept for the old ROAP PeerConnection to be aligned with WebKit naming. ROAP is planned to be removed pretty soon, then the classes can be refactored.
See also main WebKit bug https://bugs.webkit.org/show_bug.cgi?id=80589
(In particular https://bugs.webkit.org/show_bug.cgi?id=82450)
TEST=content_unittests and manual webrtc test.
Review URL: http://codereview.chromium.org/9699069
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131949 0039d316-1c4b-4281-b951-d872f2087c98
FontLoader calls file_util::GetFileSize() and file_util::ReadFile(),
which should be called from the file thread, but FontLoader runs on the
io thread now. Make it run on the file thread.
BUG=108645
TEST=none
Review URL: http://codereview.chromium.org/9950141
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131324 0039d316-1c4b-4281-b951-d872f2087c98
Also collapses some long parameter lists into AudioParameters and moves some
of the hardcoded values (e.g. 16 bit audio in AudioDevice) to more appropriate
locations.
BUG=115902
TEST=manually testing everything works out
Review URL: https://chromiumcodereview.appspot.com/9655018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128054 0039d316-1c4b-4281-b951-d872f2087c98
We do not want to use the accelerated 2d canvas path if we can lose a context
"too easily" - for example due to the screensaver turning on - or if we're using
a software rendering backend for GL contexts (swiftshader). The way these conditions
are currently checked for are awkard and racy. This adds an explicit check that
WebKit calls prior to instantiating an accelerated context for canvas. This
does two things:
1.) Attempt to spin up the GpuChannelHost. If we can't do this, then we definitely
don't need to bother. Note that if the GPU process crashes this will establish a
connection to the new GPU process.
2.) Query the can_lose_context and software_rendering bits from the new channel.
These are both properties of the GPU process, not of individual contexts, so we
don't need to have a particular context ready in order to do this.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/9655017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126558 0039d316-1c4b-4281-b951-d872f2087c98
GpuChannelHostFactory itself is no longer a singleton, we pass it explicitly to
WebGraphicsContext3DCommandBufferImpl. That prevents RenderThreadImpl and
BrowserGpuChannelHostFactory from stomping on each other in --single-process
mode
BUG=117594
TEST=see bug
Review URL: http://codereview.chromium.org/9667012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126194 0039d316-1c4b-4281-b951-d872f2087c98
This is needed for using compositor filters in Aura such as glass blur.
BUG=99528
TEST=
Review URL: http://codereview.chromium.org/9568042
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124594 0039d316-1c4b-4281-b951-d872f2087c98
This patch:
- renames content/{common,browser]/file_system to content/{common,browser}/fileapi,
- moves content/browser/chrome_blob_storage_context.{h,cc} into content/browser/fileapi,
- moves content/common/webblob_registry_impl.{h,cc} into content/common/fileapi,
- moves content/common/{file_system_messages.h,webblob_messages.h} into content/common/fileapi,
- adds jianli@ to OWNERS of content/{browser,common}/fileapi,
- rename FileAndBlobMessageFilter to FileAPIMessageFilter.
BUG=115603
TEST='Build should finish successfully'
Review URL: http://codereview.chromium.org/9558006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124439 0039d316-1c4b-4281-b951-d872f2087c98
Also excludes usage of WebMediaPlayerImpl from render_view_impl.cc as it will be
implemented differently for android in a future CL. These changes are required to
make progress in getting content_unittests link for android.
BUG=113218
TEST=
Review URL: http://codereview.chromium.org/9361039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121095 0039d316-1c4b-4281-b951-d872f2087c98
A future CL will move them out of content/renderer so that they can be used by
the browser process.
All requests to singleton-like things - e.g. establish a channel to the GPU
process - go through a GpuChannelHostFactory, implemented by RenderThreadImpl.
BUG=99516
TEST=manually tested Chrome with accelerated content.
Review URL: http://codereview.chromium.org/9270025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120701 0039d316-1c4b-4281-b951-d872f2087c98
This needs https://bugs.webkit.org/show_bug.cgi?id=76593 to land first.
This also removes WebKitPlatformSupport::createGraphicsContext3D implementations that are not called any more after the above.
BUG=None
TEST=chrome with accelerated content, DRT, test_shell_tests
Review URL: http://codereview.chromium.org/9226036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120431 0039d316-1c4b-4281-b951-d872f2087c98
