summaryrefslogtreecommitdiffstats
path: root/content
Commit message (Collapse)AuthorAgeFilesLines
* Revert 187427 "PPAPI: Remove threading options; it's always on"karen@chromium.org2013-03-122-1/+4
| | | | | | | | | | | | | | | | | | | | | > PPAPI: Remove threading options; it's always on > > This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere. > > BUG=159240,92909 > > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186925 > Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=186939 due to build errors > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=187340 > > Review URL: https://chromiumcodereview.appspot.com/12378050 TBR=dmichael@chromium.org Review URL: https://codereview.chromium.org/12805002 git-svn-id: svn://svn.chromium.org/chrome/branches/1438/src@187668 0039d316-1c4b-4281-b951-d872f2087c98
* [mac] Fix 'hidden' property in app windows.jeremya@chromium.org2013-03-121-2/+5
| | | | | | | | | | | | Fixed by making WebContentsViewMac::Focus not call -makeKeyAndOrderFront: if the window isn't visible. BUG=177706 Review URL: https://chromiumcodereview.appspot.com/12692003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187497 0039d316-1c4b-4281-b951-d872f2087c98
* Windows: Detect whether Lenovo dCute is installed.apatrick@chromium.org2013-03-125-0/+30
| | | | | | | | | | | | The associated Thinkpad USB Port Replicator driver can crash on GPU process startup. This patch is just to detect it and note its presence in about:gpu. The fix for the crash itself will be separate. BUG=181665 Review URL: https://chromiumcodereview.appspot.com/12566026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187478 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 170568 - Do DXVA pre-sandbox initialization off the main thread.apatrick@chromium.org2013-03-124-67/+42
| | | | | | | | | | Drivers for DisplayLink and Thinkpad USB Port Replicator crash when Direct3D is initialized on a sandboxed worker thread. BUG=181665,177611 Review URL: https://chromiumcodereview.appspot.com/12408016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187470 0039d316-1c4b-4281-b951-d872f2087c98
* Android: Fix crash in WebrtcBrowserTest.nileshagrawal@chromium.org2013-03-121-2/+1
| | | | | | | | | | On Android the test server is a remote test server and needs to be started on the main thread. BUG=181069 Review URL: https://chromiumcodereview.appspot.com/12743003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187466 0039d316-1c4b-4281-b951-d872f2087c98
* Android: Enable --composite-to-mailboxsievers@chromium.org2013-03-122-0/+6
| | | | | | | | BUG=181640 Review URL: https://chromiumcodereview.appspot.com/12734002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187465 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Chromify the Animation and LayerAnimationController classesdanakj@chromium.org2013-03-121-1/+1
| | | | | | | | | | | | | Style-only change. Make the Animation, AnimationEvent, AnimationCurve, KeyframedAnimationCurve, and LayerAnimationController classes use chromium style. R=jamesr,enne TBR=piman Review URL: https://codereview.chromium.org/12517003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187463 0039d316-1c4b-4281-b951-d872f2087c98
* ContextProvider::BindToCurrentThread should fail consistently.danakj@chromium.org2013-03-121-2/+4
| | | | | | | | | | | | | | | | | BindToCurrentThread() should not return true if makeContextCurrent() fails. If makeContextCurrent() fails, then the context will not have a valid GLES2Implementation or GLES2CmdHelper. So make sure BindToCurrentThread() always returns false in this situation. Currently, the second time the function is called it will return true no matter what, which is awful. R=piman BUG=181636 Review URL: https://codereview.chromium.org/12667020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187456 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Prevent crash when context creation fails.danakj@chromium.org2013-03-121-3/+4
| | | | | | | | | | | | | | | If context creation fails, don't store the context provider. Otherwise, when WebKit asks for the GrContext, we create it with a WebGraphicsContext3D which cannot be made current, and this causes a crash in skia. We already know that the Context3D is no good, because BindToCurrentThread() on the provider failed. So we can avoid giving skia the Context3D and having it crash. BUG=180911 Review URL: https://chromiumcodereview.appspot.com/12771011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187434 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Remove threading options; it's always ondmichael@chromium.org2013-03-122-4/+1
| | | | | | | | | | | | | | | | This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere. BUG=159240,92909 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186925 Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=186939 due to build errors Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=187340 Review URL: https://chromiumcodereview.appspot.com/12378050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187427 0039d316-1c4b-4281-b951-d872f2087c98
* Add check to ensure that transport dib size is larger than the size of the ↵cdn@chromium.org2013-03-121-0/+2
| | | | | | | | | | damage buffer. BUG=168901 TEST=N/A Review URL: https://codereview.chromium.org/12755015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187426 0039d316-1c4b-4281-b951-d872f2087c98
* Deflake insertion handle testscjhopman@chromium.org2013-03-123-187/+199
| | | | | | | | | | | | | | | | | There are several changes to fix these tests: Disable zoom on the test html pages. Make the initial events sent to make the insertion handles be displayed much more robust. Workaround bug in bad updateFrameInfo calls. Fix inconsistencies in handling the handle's vertical offset. Use DOMUtils to determine click locations instead of hard-coded values. BUG=169648 Review URL: https://chromiumcodereview.appspot.com/12731005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187422 0039d316-1c4b-4281-b951-d872f2087c98
* Adds a chrome://accessibility page, which:aboxhall@chromium.org2013-03-1212-1/+601
| | | | | | | | | | | | | Adds a toggle for global accessibility mode (on/off) For each renderer: - shows an accessibility mode toggle - if accessibility mode is On, shows a 'Show(/hide) accessibility tree' toggle, which shows(/hides) a text representation of the accessibility tree inline in the page. The accessibility tree may also be refreshed. BUG=178756 Review URL: https://chromiumcodereview.appspot.com/11791028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187417 0039d316-1c4b-4281-b951-d872f2087c98
* Replace hand-written JNI in fling_animator with generated bindings.yfriedman@chromium.org2013-03-111-0/+2
| | | | | | | | | | Using generated bindings are safer, and we're trying to remove existing manual bindings. Review URL: https://chromiumcodereview.appspot.com/12638003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187409 0039d316-1c4b-4281-b951-d872f2087c98
* Fix test flakiness: RenderWidgetHostViewBrowserTest.MacFrameSubscriberTesthclam@chromium.org2013-03-111-3/+5
| | | | | | | | | | | | | This change fixed test flakiness by doing multiple window resizes to make sure there is actually a repaint. BUG=18019 TEST=RenderWidgetHostViewBrowserTest.MacFrameSubscriberTest is not flaky Review URL: https://chromiumcodereview.appspot.com/12612009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187408 0039d316-1c4b-4281-b951-d872f2087c98
* Wrap calls to GetTouchInputInfogirard@chromium.org2013-03-111-2/+3
| | | | | | | | | | | This function is not available before Win7. BUG=181073 Review URL: https://chromiumcodereview.appspot.com/12566007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187406 0039d316-1c4b-4281-b951-d872f2087c98
* mac content shell drt: Don't DLOG(FATAL) during font loading in debug buildsthakis@chromium.org2013-03-112-5/+8
| | | | | | | | | | | | | | | | | | The problem was that `[[NSBundle mainBundle] bundlePath]` returned Content Shell.app's bundle in debug builds, but Content Shell.app/Contents/Versions/Content Shell Helper.app's bundle in debug builds. This is already handled in content/shell/paths_mac.mm, so use the code in there (and move the initialization for that code to happen before WebKitTestPlatformInitialize is called). BUG=179805 TEST=`echo compositing/absolute-position-changed-in-composited-layer.html | out/Debug/Content\ Shell.app/Contents/MacOS/Content\ Shell --dump-render-tree` passes. Review URL: https://codereview.chromium.org/12470006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187402 0039d316-1c4b-4281-b951-d872f2087c98
* Protect ChromeOS video decode accelerators initialization with ifdef USE_X11spang@chromium.org2013-03-111-4/+4
| | | | | | | | These features only work on X11 currently. This is needed for non-X11 builds on Linux. Review URL: https://chromiumcodereview.appspot.com/12476027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187399 0039d316-1c4b-4281-b951-d872f2087c98
* Aura on Windows: Show a system error if we can startcpu@chromium.org2013-03-111-2/+14
| | | | | | | | | | | | | | | | | | | | | | If we fail to initialize |OffscreenContextProviderForMainThread| we are dead in the water, unable to show UI, currently we just silently crash. With this change we still take a dump but now we show a system message, which reads "A GPU exception was detected on the given device. The device cannot be scheduled." This message is not shown by chrome, it is shown by CSRSS. Also this code liekly be removed in the future, with more work we might be able to show a better dialog or to simply switch to software compositor in a seamless manner. BUG=175262 R=piman Review URL: https://chromiumcodereview.appspot.com/12436008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187398 0039d316-1c4b-4281-b951-d872f2087c98
* Enforce that content interfaces around internal implementations are not ↵jam@chromium.org2013-03-114-0/+18
| | | | | | | | | | | overridden by embedders. There are two main reasons: -content needs to be able to freely cast from the interfaces to its concrete types -we don't want to update n classes in embedders, or break their tree, when we modfiy content interfaces Review URL: https://codereview.chromium.org/12542012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187395 0039d316-1c4b-4281-b951-d872f2087c98
* Use multiple shared memory buffers cyclically for audio capture.wjia@chromium.org2013-03-119-34/+79
| | | | | | | | | | | | | Currently, only one buffer of shared memory (10ms) is used to transfer captured audio data from browser process to renderer process. This results in data overwriting on both desktop and mobile, since it gives renderer process only 10ms to pick up the data and renderer process will likely miss reading data in time from time to time due to various reasons, e.g., thread scheduling. This patch adds a scheme using multiple buffers of shared memory cyclically so that renderer process can have much more time to pick up the data. This can mitigate most data owerwriting cases which happen typically in burst mode. This approach does not introduce any new delay in browser process. The number of buffers is currently set to 10. It can be set to any positive number and be tuned if needed. BUG=178040 Review URL: https://codereview.chromium.org/12379071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187393 0039d316-1c4b-4281-b951-d872f2087c98
* Provide DevToolsHttpHandlerDelegate with an ability to provide additional ↵mnaganov@chromium.org2013-03-115-0/+17
| | | | | | | | | | | | | | page info For imlementing Android WebView remote debugging, it makes a lot of sense to provide additional information about debuggable WebViews besides the page title. This is because WebView-based apps can have a lot of WebViews with no sensible titles, so picking the one needed becomes a real issue. Review URL: https://chromiumcodereview.appspot.com/12472004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187383 0039d316-1c4b-4281-b951-d872f2087c98
* Fix InterProcessTimeTicksConverter in the case thatmmenke@chromium.org2013-03-113-79/+123
| | | | | | | | | | | | | | | | | | remote range < local range. The new code maps the entire remote range onto the entire local range. Also accepts "null" input times and leaves them untouched. This is needed before the new load timing code can be hooked up (https://codereview.chromium.org/12094085/), as it will sometimes result in requestStart being before fetchStart otherwise. BUG=174170 Review URL: https://chromiumcodereview.appspot.com/12453003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187363 0039d316-1c4b-4281-b951-d872f2087c98
* Disable WebContentsVideoCaptureDeviceTest.RejectsInvalidAllocateParamsccameron@chromium.org2013-03-111-1/+6
| | | | | | | | | BUG=181594 TBR=nick@chromium.org,wjia@chromium.org Review URL: https://chromiumcodereview.appspot.com/12566018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187355 0039d316-1c4b-4281-b951-d872f2087c98
* Avoid sending nonempty view size with empty backing size.aelias@chromium.org2013-03-111-0/+6
| | | | | | | | | | | | | | | | | | | | | This condition, which occurs during EmbedContentViewActivity initialization, results in a white-screen state because of the following sequence: 1. pending_resize_ack_ is set in RWHI. 2. didCompleteSwapBuffers is never called in RenderWidget because of the empty backing, therefore the resize ack is never sent. 3. When the backing size is set to a nonzero value, RWHI refuses to send it because it expects a pending resize. We can avoid this situation by returning 0 from GetViewBounds as well until the backing is initialized. BUG=181244 Review URL: https://chromiumcodereview.appspot.com/12430010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187347 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 187340 "PPAPI: Remove threading options; it's always on"dmichael@chromium.org2013-03-112-1/+4
| | | | | | | | | | | | | | | | | | | > PPAPI: Remove threading options; it's always on > > This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere. > > BUG=159240,92909 > > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186925 > Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=186939 due to build errors > > Review URL: https://chromiumcodereview.appspot.com/12378050 TBR=dmichael@chromium.org Review URL: https://codereview.chromium.org/12476028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187346 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Remove threading options; it's always ondmichael@chromium.org2013-03-112-4/+1
| | | | | | | | | | | | | | This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere. BUG=159240,92909 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186925 Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=186939 due to build errors Review URL: https://chromiumcodereview.appspot.com/12378050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187340 0039d316-1c4b-4281-b951-d872f2087c98
* Web Content zoom settings should not apply to login/lock screenantrim@chromium.org2013-03-1110-39/+190
| | | | | | | | | | | | | | | Add scheme to HostZoomMap, use it to specify unmodifiable zoom level for internal ui pages. Reason : Currently, zoom settings are remebered on a per-host basis, and ignore scheme. It works nice for http/https access for the same host, but it is not possible to distinguish between internal ui (with chrome:// scheme) and some intranet sites (having https://login/ does not seem unlikely). BUG=164269 Review URL: https://chromiumcodereview.appspot.com/11866004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187331 0039d316-1c4b-4281-b951-d872f2087c98
* IndexedDB: Re-enable IndexedDBLayoutTest.IndexTests jsbell@chromium.org2013-03-111-4/+1
| | | | | | | | | | | | | | The index-multientry.html layout test was flaky in multiprocess due to a race between IPC and event processing. http://trac.webkit.org/changeset/145111 TBR=dgrogan@chromium.org BUG=153064 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/12414013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187321 0039d316-1c4b-4281-b951-d872f2087c98
* Do not show pages of swapped out RenderViewHosts in DevTools remote debuggingmnaganov@chromium.org2013-03-111-0/+5
| | | | | | | | | | | | | | RenderViewHosts can be swapped out for performance and cross-scripting purposes (see the full discussion here: https://groups.google.com/a/chromium.org/d/topic/chromium-dev/e-M4HgwpDp8/discussion) It makes no sense reporting the corresponding views on DevTools remote debugging landing pages. Review URL: https://chromiumcodereview.appspot.com/12764008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187312 0039d316-1c4b-4281-b951-d872f2087c98
* Fix aura backing store to work with non-integer scale factors.kevers@chromium.org2013-03-112-10/+15
| | | | | | | | | BUG=179982 Review URL: https://chromiumcodereview.appspot.com/12389084 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187289 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 187283reed@google.com2013-03-114-87/+106
| | | | | | | | | | | | | | | | | memcheck reported errors which need to be investigated > Call version of SkFontHost_fontconfig in Skia (cloned from here). > Retool the direct/remove plumbing to use SkFontConfigInterface. > > This change allows Skia to interate on the details of SkFontHost w/o having > to synchromize with chrome on each change. It also means Skia's internal testing > can exercise exactly the same config that Chrome does. > Review URL: https://codereview.chromium.org/12391070 TBR=reed@google.com Review URL: https://codereview.chromium.org/12771003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187287 0039d316-1c4b-4281-b951-d872f2087c98
* Call version of SkFontHost_fontconfig in Skia (cloned from here).reed@google.com2013-03-114-106/+87
| | | | | | | | | | | Retool the direct/remove plumbing to use SkFontConfigInterface. This change allows Skia to interate on the details of SkFontHost w/o having to synchromize with chrome on each change. It also means Skia's internal testing can exercise exactly the same config that Chrome does. Review URL: https://codereview.chromium.org/12391070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187283 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 187230zork@chromium.org2013-03-1114-689/+0
| | | | | | | | | | | | | | | | | | | > Implement the Stream registry in content > > This is the first part of the content side of the Streams api. > See: > https://bugs.webkit.org/show_bug.cgi?id=110194 > https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm > > BUG=171585 > > > Review URL: https://chromiumcodereview.appspot.com/12335087 TBR=zork@chromium.org Review URL: https://codereview.chromium.org/12611018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187274 0039d316-1c4b-4281-b951-d872f2087c98
* Adds support of local audio streams for more than one media player.henrika@chromium.org2013-03-117-344/+262
| | | | | | | | | | | | | | | | | | | Main goal is to allow the user to use a local stream as source for more than one audio element. Adding the stream to one extra element will result in an increased output volume and the possibility to tune the volume on each element. If two elements are used, both elements must be muted to silence the audio. The design is now more clear since more work is done in the local renderer and not divided between the capturer (which used to own the FIFO) and the local renderer. The capturer only dispatches the recorded audio out to its sinks and they deal with the rest. - Removes auto-mute on local media streams when rendered by a media player. - Moves local FIFO from WebRtcAudioCapturer to WebRtcLocalAudioRenderer. - Now allows multiple WebRtcLocalAudioRenderer objects where each instance creates its own output stream. - Adds support for the enabled attribute on the MediaStreamTrack object. BUG=none TEST=All existing WebRTC demos and a new test at: https://www.corp.google.com/~henrika/webrtc/multi_local_rendering.html TBR=wjia@chromium.org Review URL: https://codereview.chromium.org/12599002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187252 0039d316-1c4b-4281-b951-d872f2087c98
* Implement the Stream registry in contentzork@chromium.org2013-03-1114-0/+689
| | | | | | | | | | | | | | This is the first part of the content side of the Streams api. See: https://bugs.webkit.org/show_bug.cgi?id=110194 https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm BUG=171585 Review URL: https://chromiumcodereview.appspot.com/12335087 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187230 0039d316-1c4b-4281-b951-d872f2087c98
* Initial implementation of the permission API for Browser Plugin PointerLockmthiesse@chromium.org2013-03-107-35/+64
| | | | | | | | | | | | | | Exposed permission event parameters: userGesture - true if the lock request originated from a user gesture. lastUnlockedBySelf - true if the a previous mouse lock to the page was unlocked by the page itself (i.e. not through a user alt+tabbing out). originUrl - the URL of the page the request originated from. BUG=166228 Review URL: https://chromiumcodereview.appspot.com/12455011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187221 0039d316-1c4b-4281-b951-d872f2087c98
* Roll libjingle 291:294.ronghuawu@chromium.org2013-03-101-1/+1
| | | | | | | Fix a bug in content_browsertest (callWithoutMsidAndBundle). It works previously because there's another bug in sdp parser, so two wrongs make it right. Review URL: https://codereview.chromium.org/12717003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187188 0039d316-1c4b-4281-b951-d872f2087c98
* Update some #includes for WebMessagePortChannel.h which has moved to ↵pilgrim@chromium.org2013-03-093-3/+3
| | | | | | | | Platform/ upstream Review URL: https://chromiumcodereview.appspot.com/12631002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187175 0039d316-1c4b-4281-b951-d872f2087c98
* Make chromeos gpu_video_decode_accelerator depend on X11spang@chromium.org2013-03-092-6/+6
| | | | | | | | These ChromeOS video decode accelerators are currently dependent on X11. Make that explicit so X11-less builds can work. Review URL: https://chromiumcodereview.appspot.com/12631014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187164 0039d316-1c4b-4281-b951-d872f2087c98
* Properly hook the RenderWidgetFullscreenPepper to the frame counting logic.piman@chromium.org2013-03-092-9/+17
| | | | | | | | | | | | | This was broken by r130094, forgetting to set up the WebGraphicsContext3DSwapBuffersClient onto the WebGraphicsContext3DCommandBufferImpl. BUG=180332 Review URL: https://chromiumcodereview.appspot.com/12738004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187160 0039d316-1c4b-4281-b951-d872f2087c98
* ContentViewScrollTest cleanup and scroll testdfalcantara@chromium.org2013-03-091-34/+81
| | | | | | | | | | | | Replace the scroll test from downstream with an upstream one. Refactors the fling test so that they can share code. BUG=147939 Review URL: https://chromiumcodereview.appspot.com/12621006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187155 0039d316-1c4b-4281-b951-d872f2087c98
* Disable failing VerifyNPObjectLifetimeTest on Win64jschuh@chromium.org2013-03-091-1/+1
| | | | | | | | | BUG=180861 TBR=piman@chromium.org R=piman@chromium.org Review URL: https://codereview.chromium.org/12502008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187147 0039d316-1c4b-4281-b951-d872f2087c98
* Implemented browser side software compositing behind the ↵skaslev@chromium.org2013-03-097-40/+274
| | | | | | | | | | --ui-enable-software-compositing flag. BUG=124671, 161008 Review URL: https://chromiumcodereview.appspot.com/12542006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187123 0039d316-1c4b-4281-b951-d872f2087c98
* Clarify AutoResizeCompositor should only be called in auto resize mode.aelias@chromium.org2013-03-094-7/+12
| | | | | | | | | | | | | | As seen in https://codereview.chromium.org/12544017/, the temptation to hack around resize bugs by just calling AutoResizeCompositor is strong. Move the guard for enable_auto_resize_ inside it to better document the recommended use. NOTRY=true BUG=180999 Review URL: https://chromiumcodereview.appspot.com/12639005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187117 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed crash when setDeviceScaleFactor is called too earlyjscholler@chromium.org2013-03-091-1/+2
| | | | | | | | | | | | | | Some intrumentation test was calling setDeviceScale very early, before the host of the compositorImpl for Android was created. This CL add a small check to prevent the crash. Needed for BUG=175589 Review URL: https://chromiumcodereview.appspot.com/12497011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187115 0039d316-1c4b-4281-b951-d872f2087c98
* pepper: Use the RenderThread's shared context as the parent context.danakj@chromium.org2013-03-099-164/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* <browser>: permissionRequest API for geolocation.lazyboy@chromium.org2013-03-0910-9/+257
| | | | | | | | | | BUG=141195 TEST=Added browsertests: WebViewTest.GeolocationAPI* Review URL: https://chromiumcodereview.appspot.com/11142012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187099 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 187073crogers@google.com2013-03-092-8/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This re-lands 187048 BUG=none TEST=none TBR=ccameron@chromium.org > Revert 187048 > based on > http://build.chromium.org/p/chromium.win/builders/Win%20Aura%20Tests%20%282%29/builds/1968 > > > Enable the "Web Audio Input" feature by default. > > > > We now get the proper audio input device identifier passed into WebKit and back into chromium > > to be able to determine if the correct device will be used that the user gave permission to > > access in getUserMedia(). > > > > See related WebKit work: > > https://bugs.webkit.org/show_bug.cgi?id=90110 > > https://bugs.webkit.org/show_bug.cgi?id=93756 > > https://bugs.webkit.org/show_bug.cgi?id=101815 > > https://bugs.webkit.org/show_bug.cgi?id=106490 > > https://bugs.webkit.org/show_bug.cgi?id=106816 > > https://bugs.webkit.org/show_bug.cgi?id=109494 > > https://bugs.webkit.org/show_bug.cgi?id=110796 > > > > and chromium work: > > https://codereview.chromium.org/10830268/ > > https://codereview.chromium.org/10916105/ > > https://codereview.chromium.org/10909185/ > > https://codereview.chromium.org/10959068 > > https://codereview.chromium.org/11418125/ > > https://codereview.chromium.org/11827040/ > > https://codereview.chromium.org/11878032/ > > https://codereview.chromium.org/12218106/ > > https://codereview.chromium.org/12335072/ > > > > BUG=145092 > > TEST=none > > manual tests: > > http://chromium.googlecode.com/svn/trunk/samples/audio/visualizer-live.html > > http://dashersw.github.com/pedalboard.js/demo/ > > Review URL: https://codereview.chromium.org/12383064 > > TBR=crogers@google.com > Review URL: https://codereview.chromium.org/12649007 TBR=ccameron@chromium.org Review URL: https://codereview.chromium.org/12743002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187095 0039d316-1c4b-4281-b951-d872f2087c98
* Rename font_list_x11 to font_list_linuxspang@chromium.org2013-03-092-1/+1
| | | | | | | | | This file does not depend on X11, only pango. Review URL: https://chromiumcodereview.appspot.com/12703002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187094 0039d316-1c4b-4281-b951-d872f2087c98