summaryrefslogtreecommitdiffstats
path: root/content/browser/renderer_host
Commit message (Collapse)AuthorAgeFilesLines
* Mac ÜC: Enable back-pressure for the browser compositorccameron@chromium.org2014-06-121-0/+1
| | | | | | | | | | | Delay acknowledging the cc::OutputSurface's swap completion until the surface is displayed. BUG=314190 Review URL: https://codereview.chromium.org/334593002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276629 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Java Bridge with Gin: implement Java methods invocationmnaganov@chromium.org2014-06-126-0/+1468
| | | | | | | | | | | | | | | | | | | | | | | | This patch adds GinJavaMethodInvocationHelper class which serves for coercion of arguments and return values of Java methods to / from base::Value and GinJavaBridgeValue. The coercion code is taken from the existing implementation (JavaBoundObject) with required conversions to use base::Value and GinJavaBridgeValue instead of NPVARIANT and friends. There are extensive Java tests for coercion, so here we only add some unit tests for edge cases. This patch also adds a trivial EventLog class for writing into Android Event Log from C++ code. BUG=355644 R=bulach@chromium.org, torne@chromium.org TBR=brettw@chromium.org Review URL: https://codereview.chromium.org/302173006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276586 0039d316-1c4b-4281-b951-d872f2087c98
* Support minimum gesture bounds in GestureProviderjdduke@chromium.org2014-06-121-1/+1
| | | | | | | | | | | | | | | | Some touch devices report either zero or unreasonably small touch sizes. While this doesn't present a problem for gesture detection, it does affect the behavior of the touch-derived gestures. For example, tap disambiguation is prevented if the tap gesture's size is sufficiently small. As a workaround, provide a platform-specific minimum gesture bounds length in GestureProvider. On Android, this value is the same as was used before the unified gesture detector, and on Aura we simply use half the default touch size. BUG=379876 Review URL: https://codereview.chromium.org/321563002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276550 0039d316-1c4b-4281-b951-d872f2087c98
* Android: Schedule composite immediately when requested by frontendsievers@chromium.org2014-06-121-1/+1
| | | | | | | | | BUG=382675 NOTRY=True Review URL: https://codereview.chromium.org/334533002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276528 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce WebFallbackFont on the Chromium sidedominik.rottsches@intel.com2014-06-122-10/+16
| | | | | | | | | | | | | Patch 2 in the series of renaming WebFontFamily to WebFallbackFont, at the same time, fixing the sandbox support IPC to transmit filename and ttcIndex. Depends on step 1 of the rename, r175858 in Blink. BUG=382411 R=eae,behdad,jln,piman Review URL: https://codereview.chromium.org/327633002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276520 0039d316-1c4b-4281-b951-d872f2087c98
* Re-allow PreCacheFont for GDI access for pdf.dllscottmg@chromium.org2014-06-112-5/+9
| | | | | | | | | | | | | This was turned off when DirectWrite is on, however pdf still needs access to them in process. R=jschuh@chromium.org TBR=jam@chromium.org, jschuh@chromium.org BUG=383227 Review URL: https://codereview.chromium.org/331463002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276488 0039d316-1c4b-4281-b951-d872f2087c98
* Remove lazy layout preference plumbingjchaffraix@chromium.org2014-06-111-2/+0
| | | | | | | | | This is dead code as the Blink bits were removed in http://src.chromium.org/viewvc/blink?view=revision&revision=156126 Review URL: https://codereview.chromium.org/326823003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276417 0039d316-1c4b-4281-b951-d872f2087c98
* Allocate SharedBitmaps on FILE_USER_BLOCKING thread.jbauman@chromium.org2014-06-112-7/+27
| | | | | | | | | | Allocating these can be expensive (especially on OS X) so it's best not to block the IO thread while doing that. BUG= Review URL: https://codereview.chromium.org/317973004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276358 0039d316-1c4b-4281-b951-d872f2087c98
* Scroll offset pinning and content size notifications were only used for the ↵avi@chromium.org2014-06-119-62/+0
| | | | | | | | | | | | | Mac overlay navigation code, which no longer needs them as of r274906. Remove them. BUG=321437 TEST=everything still compiles and works. Review URL: https://codereview.chromium.org/325933003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276217 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce the ENABLE_BROWSER_CDMS macro.xhwang@chromium.org2014-06-103-8/+11
| | | | | | | | | | | | | | | | | | | | | This will be defined when a platform needs to use browser side CDM to implement EME API. Currently this is only used on Android. Note that MediaWebContentsObserver is shared by Android media player managers and browser CDM managers. Since ENABLE_BROWSER_CDMS is always true on Android, we only check ENABLE_BROWSER_CDMS to decide whether MediaWebContentsObserver should be used. Also, in media_web_contents_observer.*, we only check OS_ANDROID to decide whether Android media player code should be used. This is not perfect but makes the current code simple. This will be fixed when we have a general (not Android specic) media player manager. TBR=yfriedman@chromium.org BUG=315312 TEST=Compiles on Android. Test pages still work on Android. Compiles when I choose to use browser CDM on Linux. Review URL: https://codereview.chromium.org/318753010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276200 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ForceCompositingMode from switches and WebPreferences.danakj@chromium.org2014-06-101-1/+0
| | | | | | | | | | | This is always on, no need to have a web pref or a command line flag. R=piman BUG=363772 Review URL: https://codereview.chromium.org/328473002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276146 0039d316-1c4b-4281-b951-d872f2087c98
* Invert DSF to map from delegated frame to layer spacejamesr@chromium.org2014-06-102-2/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The size of the frame data from a delegated source will not in general match up exactly with the delegated layer's bounds. Frame sizes and layer bounds are both expressed as integers, but frame sizes are in physical pixels and layer bounds are in device-independent pixels. If the device scale is not an integer, there may not be an exact mapping between the two spaces. For instance, if the layer size is 105 x 211 and the device scale is 1.5, the delegated content is responsible for filling 157.5 x 316.5 physical pixels in the final output. This isn't really possible so what actually happens is the delegated renderer produces a frame with a physical size of 158 x 317 pixels and sends that up to the DRLI. To map this frame into physical space, the DRLI should apply the inverse of the device scale factor to reflect that the frame covers 105.333 x 211.3333 logical pixels. Before this patch, DRLI would attempt to scale the frame by (105/158, 211/317) resulting in the frame being scaled down non-uniformly to try to make 158 x 317 pixels fit into a 157.5 x 316.6 space. This scaling looks bad and ends up mapping pixels partially outside of the layer's logical bounds into the layer's logical bounds. BUG=370074 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=275544 Review URL: https://codereview.chromium.org/311253004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276139 0039d316-1c4b-4281-b951-d872f2087c98
* Remove swap ack throttling.ccameron@chromium.org2014-06-103-72/+3
| | | | | | | | | | | | This will be implemented at a different level, reverting the non-useful parts of r275478 TBR=jbauman BUG=314190 Review URL: https://codereview.chromium.org/326563003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276066 0039d316-1c4b-4281-b951-d872f2087c98
* Use the provided connection type to determine if online.jkarlin@chromium.org2014-06-101-1/+2
| | | | | | | | | | Calling IsOffline() could race and return an answer for a different type. BUG=381282 Review URL: https://codereview.chromium.org/317933002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276050 0039d316-1c4b-4281-b951-d872f2087c98
* Disable overscroll navigation when emulating touch.dgozman@chromium.org2014-06-102-0/+6
| | | | | | | | | | | | | | | When emulating another device in DevTools (including touch), overscroll navigation is confusing for the user: - if device does not support touch, user is not used to the overscroll navigation and may be surprised; - with content not filling the whole view, overscroll navigation looks unnatural. BUG=369938 Review URL: https://codereview.chromium.org/313083002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276019 0039d316-1c4b-4281-b951-d872f2087c98
* Move SnapToPhysicalPixelBoundary call to RWHVA::InternalSetBoundsjamesr@chromium.org2014-06-101-4/+2
| | | | | | | | | | | | | RWHVAura::SetBounds isn't actually called in most situations, so the snapping wasn't occuring when it should. ::SetSize is actually called when the bounds of the RWHVA changes and both call ::InternalSetBounds(), so this calls the snapping logic there. BUG=370074 Review URL: https://codereview.chromium.org/317633006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275994 0039d316-1c4b-4281-b951-d872f2087c98
* Move about://-related constants from //content to //urlblundell@chromium.org2014-06-102-7/+8
| | | | | | | | | | | kAboutScheme and kAboutBlankURL are used in code shared by iOS, and are general enough to live in //url instead of //content. TBR=yoz,benm Review URL: https://codereview.chromium.org/325443002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275988 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 275853 "Temporarily disable media stream audio track proc..."wittman@chromium.org2014-06-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | Breaks browser test PPAPINaClPNaClTest.MediaStreamAudioTrack on Mac: http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac%2010.6%20Tests%20%28dbg%29%284%29&number=41869 > Temporarily disable media stream audio track processing. > > > NOTRY=true > > TBR=jochen@chromium.org > BUG=382094 > TEST=bots > > Review URL: https://codereview.chromium.org/320813002 TBR=xians@chromium.org Review URL: https://codereview.chromium.org/328443004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275863 0039d316-1c4b-4281-b951-d872f2087c98
* Enable DirectWrite by defaultscottmg@chromium.org2014-06-091-1/+1
| | | | | | | | | | | | Flips the sense of the flag for now. If all seems OK as we move through channels, I will remove it later. R=cpu@chromium.org, jam@chromium.org BUG=25541 Review URL: https://codereview.chromium.org/323563005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275860 0039d316-1c4b-4281-b951-d872f2087c98
* Temporarily disable media stream audio track processing.xians@chromium.org2014-06-091-1/+1
| | | | | | | | | | | | NOTRY=true TBR=jochen@chromium.org BUG=382094 TEST=bots Review URL: https://codereview.chromium.org/320813002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275853 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 275781 "Revert 273044 "Change kEnableAudioTrackProcessing..."xians@chromium.org2014-06-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | > Revert 273044 "Change kEnableAudioTrackProcessing to a disable f..." > > > Change kEnableAudioTrackProcessing to a disable flag and remove finch code for AudioTrackProcessing. > > > > The plan is to enable audio processing in getUserMedia as default for M37, and keep a kDisableAudioTrackProcessing flag to be able to fall back to the old path. > > > > BUG=365672 > > TEST=bots > > > > Review URL: https://codereview.chromium.org/293023003 > > TBR=xians@chromium.org > > Review URL: https://codereview.chromium.org/318373002 TBR=xians@chromium.org Review URL: https://codereview.chromium.org/318383002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275782 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 273044 "Change kEnableAudioTrackProcessing to a disable f..."xians@chromium.org2014-06-091-1/+1
| | | | | | | | | | | | | | | | | > Change kEnableAudioTrackProcessing to a disable flag and remove finch code for AudioTrackProcessing. > > The plan is to enable audio processing in getUserMedia as default for M37, and keep a kDisableAudioTrackProcessing flag to be able to fall back to the old path. > > BUG=365672 > TEST=bots > > Review URL: https://codereview.chromium.org/293023003 TBR=xians@chromium.org Review URL: https://codereview.chromium.org/318373002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275781 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: Do better font substitution for Chinese characters.thestig@chromium.org2014-06-081-17/+29
| | | | | | | | | | This is a reland of r260354, which accidentally got reverted in r260354. BUG=381978 Review URL: https://codereview.chromium.org/325543002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275741 0039d316-1c4b-4281-b951-d872f2087c98
* Remove fischman from WATCHLISTS and OWNERS as I am leaving the Chrome PA. ↵fischman@chromium.org2014-06-071-1/+0
| | | | | | | | | | Au revoir. TBR=vrk@chromium.org, posciak@chromium.org Review URL: https://codereview.chromium.org/322483006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275692 0039d316-1c4b-4281-b951-d872f2087c98
* Delete non-CoreAnimation code in RWHVMacccameron@chromium.org2014-06-077-624/+101
| | | | | | | | | | | | This is dead code now, and is just getting in the way. The non-CA code in ui/cocoa may still be useful for reference and debugging for a little longer, but this stuff is way past that point. BUG= Review URL: https://codereview.chromium.org/311263003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275639 0039d316-1c4b-4281-b951-d872f2087c98
* Consolidate SDK forwards in sdk_forward_declarations.h.avi@chromium.org2014-06-072-36/+1
| | | | | | | | | | BUG=none TEST=none TBR=ben@chromium.org Review URL: https://codereview.chromium.org/322623002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275578 0039d316-1c4b-4281-b951-d872f2087c98
* Add missed NULL check in r274802ccameron@chromium.org2014-06-061-0/+3
| | | | | | | | | TBR=miu BUG=381542 Review URL: https://codereview.chromium.org/319183003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275525 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize the bitmap before drawing the VideoFrame into it, in casedanakj@chromium.org2014-06-061-1/+1
| | | | | | | | | | | not everything in the video frame is opaque. R=reed@google.com, sievers@chromium.org BUG=380680 Review URL: https://codereview.chromium.org/319133003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275511 0039d316-1c4b-4281-b951-d872f2087c98
* Mac ÜC: Enable GPU back-pressure from the browser to the rendererccameron@chromium.org2014-06-064-9/+80
| | | | | | | | | | | | | | | When the browser compositor does a SwapBuffers to its output surface, take a lock on the compositor until that swap is displayed on the screen. This prevents the renderer from running ahead of the browser. If the renderer sends a new frame (it can send at most one), then track this event, and request redraw as soon as the lock is released. BUG=314190 Review URL: https://codereview.chromium.org/316103004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275478 0039d316-1c4b-4281-b951-d872f2087c98
* Remove dead notification for number of wheel event handlersskyostil@chromium.org2014-06-062-6/+0
| | | | | | | | | | Turns out no-one needs this. BUG=359566 Review URL: https://codereview.chromium.org/315653003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275467 0039d316-1c4b-4281-b951-d872f2087c98
* When deleting a WebContents, keep SessionStorageNamespaces used in the tab ↵michaeln@chromium.org2014-06-066-0/+111
| | | | | | | | | | alive until we receive an acknowledgment from the renderer that the renderer side constructs have been cleaned up. Otherwise we can receive messages from still executing content referring to sessions that were prematurely deleted. BUG=371304 Review URL: https://codereview.chromium.org/305103003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275383 0039d316-1c4b-4281-b951-d872f2087c98
* MacViews: Extend TextInputClient protocol with support for editing commands.andresantoso@chromium.org2014-06-062-0/+9
| | | | | | | | | | | | Extend TextInputClient to support validating and executing editing commands, such as IDS_DELETE_BACKWARD, IDS_MOVE_RIGHT, IDS_APP_PASTE. This will be used for implementing Textfield editing for the Mac port of Views. BUG=374077 Review URL: https://codereview.chromium.org/302293003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275294 0039d316-1c4b-4281-b951-d872f2087c98
* [Mac] Maximise timer slack for background tabsjeremy@chromium.org2014-06-051-4/+7
| | | | | | | | | | | | | | When a tab not playing audio is sent to the background, set timer slack to its maximum value. Support for setting timer slack is added at the MessageLoop level, the concrete implementation of this CL only affects CFMessagePump backed MessageLoops (which means just the main thread for backgrounded renderer processes at present). The MessageLoop implementation is designed to support its use on Windows and Linux (the Windows API sets slack per-timer like the Mac one, while on Linux slack, is set per-thread via a call to prctl() using PR_SET_TIMERSLACK). BUG=356804 Review URL: https://codereview.chromium.org/289863005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275218 0039d316-1c4b-4281-b951-d872f2087c98
* Correctly adjust DIP dynamically on Mac ÜCccameron@chromium.org2014-06-053-1/+4
| | | | | | | | | | | | Make contents scale an explicit parameter to the accelerated layer creation. This wasn't necessary in non-ÜC because the IOSurface's size was already initialized there -- in ÜC it isn't. BUG=314190 Review URL: https://codereview.chromium.org/316033003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275216 0039d316-1c4b-4281-b951-d872f2087c98
* Remove PlatformFile from DatabaseTrackerrvargas@chromium.org2014-06-051-12/+15
| | | | | | | | BUG=322664, 373095 Review URL: https://codereview.chromium.org/312003003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275185 0039d316-1c4b-4281-b951-d872f2087c98
* Add IPC::ChannelProxy::Create() and IPC::SyncChannel::Create()morrita@chromium.org2014-06-051-6/+5
| | | | | | | | | | | | | | | | | | | This change replaces constructors with Create() methods of ChannelProxy and SyncChannel. This open the possibility to introduce polymorphism to these classes. This is a revision of r274310 (https://codereview.chromium.org/301973003/) in which I added bunch of Create*() method variants. The chagne was reverted. This change no longer does it and just keeps using Channel::Mode to specify the channel type. TEST=none BUG=377980 R=darin@chromium.org,jam@chromium.org Review URL: https://codereview.chromium.org/310853003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275140 0039d316-1c4b-4281-b951-d872f2087c98
* Removing reinterpret_cast<std::vector<...> > in ↵huangs@chromium.org2014-06-051-9/+10
| | | | | | | | | | | | | | | | | | | | | RenderWidgetHostViewAura::SetCompositionText(). RenderWidgetHostViewAura::SetCompositionText() used reinterpret_cast<> to convert std::vector<ui::CompositionText> ==> std::vector<blink::WebCompositionUnderline> This requires ui::CompositionText (in Chrome) and blink::WebCompositionUnderline (in Blink) to be identical. This is problematic when we want to change blink::WebCompositionUnderline and blink::WebCompositionUnderline (and WebCore::CompositionUnderline), since Chrome & Blink CLs have to be separate. This CL implements manual copy to allow CL decoupling. BUG=135900 Review URL: https://codereview.chromium.org/319553002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275103 0039d316-1c4b-4281-b951-d872f2087c98
* Support recovery from SSL errors.ricea@chromium.org2014-06-054-17/+130
| | | | | | | | | | | | | | | | | Previously, the new WebSocket implementation was unable to handle sites with self-signed certificates and other cases where the user had overridden certificate errors. Add code to support this case. This requires adding infrastructure to pass the SSL error back up to the content layer which knows how to handle it. It also requires that the ID of the frame be known, so an extra parameter has been added to the WebSocketHostMsg_AddChannelRequest IPC message. BUG=364361 Review URL: https://codereview.chromium.org/304093003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275066 0039d316-1c4b-4281-b951-d872f2087c98
* Add requestor_url to ConnectToService()davemoore@chromium.org2014-06-041-1/+2
| | | | | | | | | R=darin@chromium.org, darin BUG= Review URL: https://codereview.chromium.org/318773002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274937 0039d316-1c4b-4281-b951-d872f2087c98
* mac: History swiping doesn't work right with iframes.erikchen@chromium.org2014-06-042-20/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL was originally intended to be a reland of https://codereview.chromium.org/227043012/. There have been sufficient changes that this CL should be given a full review. In the previous behavior, the history swiper tried to be very conservative about the gestures it recognized as a history swipe. Once a gesture was recognized, events would be consumed and not sent to the renderer. This has two fundamental flaws. 1. It is difficult to tell whether a gesture is going to be a history swipe from the initial events. Waiting for longer introduces lag in the appearance of the history swipe UI, which is janky. 2. NSEvents with phase NSEventPhaseChanged are coalesced before they are sent to the renderer. This loss of information makes it more difficult to determine which of the uncoalesced events the renderer would have handled, which adds to the difficulty of determining whether a gesture should be recognized as a history swipe. In the new behavior, the history swiper (in conjunction with the logic in ScrollElasticityController in Blink) aggressively attempts to recognize the initial events of every gesture as the beginning events of a history swipe. The recognition process is primarily gated by whether the renderer consumes the NSEvent with phase NSEventPhaseBegan. Once a gesture has been recognized as a potential history swipe, the history swipe UI is shown, and the history swiper will process new events to update its internal state, but the events will continue to be forwarded to the renderer. While the history swiper is determining whether the gesture was actually intended as a horizontal, history swipe, both itself and the renderer will get to process events and update their respective UIs. To combat the ease with which history swiping was entered, the history swiper aggressively attempts to cancel out of history swiping. If the gesture progresses sufficiently such that it appears to be intended for a history swipe, then the events will be consumed and no longer forwarded to the renderer. As an aside: the renderer callbacks for scrollOffsetPinnedToLeft and setHasHorizontalScrollbar are no longer useful. The former was not accurate to begin with, since the callback only occured when the content scrolled, but not after a history navigation. They should be removed at a convenient time. BUG=321437 Review URL: https://codereview.chromium.org/300863002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274906 0039d316-1c4b-4281-b951-d872f2087c98
* Remove flag --test-sandboxluken@chromium.org2014-06-041-1/+0
| | | | | | | | | | And associated code. BUG=352392 Review URL: https://codereview.chromium.org/285283003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274846 0039d316-1c4b-4281-b951-d872f2087c98
* Support for audio output devices for getMediaDevices.grunell@chromium.org2014-06-045-19/+97
| | | | | | | | | | | | * This CL depends on https://codereview.chromium.org/287383002/ * There's no caching or monitoring in this CL. * Browser test will be done in follow-up CL. (That's pending blink interface landing.) BUG=338511 Review URL: https://codereview.chromium.org/312773002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274823 0039d316-1c4b-4281-b951-d872f2087c98
* Ack swap buffers after a timeoutccameron@chromium.org2014-06-044-29/+82
| | | | | | | | | | | | | | | | In r272469, a timer that would automatically ack swaps after a quarter-second passed was removed. The purpose of the timer was to manage the transition between async and sync displays, but it had an unintentional side-effect of un-blocking the renderer in the event that the CALayer's display function was never called. Re-add a timer explicitly for this purpose. BUG=378445 Review URL: https://codereview.chromium.org/310183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274802 0039d316-1c4b-4281-b951-d872f2087c98
* Pepper: Use an adaptor to invoke FileSystemOperationRunner::OpenFilervargas@chromium.org2014-06-042-16/+39
| | | | | | | | | | | | | | | | PepperFileIOHost keeps a weak pointer of FileSystemOperationRunner so when it goes away it cannot delete the runner as expected by the fileapi implementation. This CL adds an adapter class in the middle so that when OpenFile completes after PepperFileIOHost destruction, the file is bounced back to another thread to be closed. BUG=377599 Review URL: https://codereview.chromium.org/306403005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274782 0039d316-1c4b-4281-b951-d872f2087c98
* Pass the device scale factor in the command line to renderer processes.ananta@chromium.org2014-06-041-0/+7
| | | | | | | | | | | | This is to ensure that we don't use GDI to query the device scale factor in renderer processes. This is in preparation for setting the MITIGATION_WIN32K_DISABLE policy on renderer processes, which will lock them out from making user32/gdi32 calls which enter win32k.sys. BUG=365160 Review URL: https://codereview.chromium.org/308003020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274766 0039d316-1c4b-4281-b951-d872f2087c98
* Remove IOSurfaceSupportccameron@chromium.org2014-06-047-79/+52
| | | | | | | | | | Link against IOSurface.framework instead -- this is an option starting in 10.6. BUG=314190 Review URL: https://codereview.chromium.org/301973010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274746 0039d316-1c4b-4281-b951-d872f2087c98
* Null check the render layer as it might be gone when video enters/exits ↵qinmin@chromium.org2014-06-041-1/+2
| | | | | | | | | | | | | fullscreen The delegated render layer can change when video enters/exits fullscreen Similar to other places in this file where layer_ is used, we should do a null check before using it. BUG=356671 Review URL: https://codereview.chromium.org/309353003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274741 0039d316-1c4b-4281-b951-d872f2087c98
* Add a TouchEventStreamValidatorjdduke@chromium.org2014-06-043-53/+33
| | | | | | | | | | | | Add touch stream validation similar to the existing gesture stream validation. Also add validation of the *output* stream from the InputRouter (in addition to the existing *input* stream validation). BUG=345372 Review URL: https://codereview.chromium.org/290473006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274740 0039d316-1c4b-4281-b951-d872f2087c98
* [Aura] Translate web contents area to nearest physical pixel boundaryjamesr@chromium.org2014-06-042-0/+23
| | | | | | | | | | | | | | | | | | | | | Views positions all views, including the views::WebView containing the aura::Window that contains the content::RenderWidgetHostViewAura, to integral DIP positions. With a non-integral device scale factor, this could position the RWHVA in between physical pixel boundaries which results in filtering the composited output from the renderer. This looks blurry and bad. This patch computes the delta to the top-left-most integer physical pixel inside the desired bounds and translates the web contents layer by that amount. This means that the top left corner of the web contents shows up at an exact physical pixel and thus the web contents is not filtered. This means that some amount on the bottom or right edge of the web contents area may be clipped, but this amount is always less that one DIP. BUG=370074, 378620 Review URL: https://codereview.chromium.org/304973003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274686 0039d316-1c4b-4281-b951-d872f2087c98
* use enum to specify deviceSource for fling animation.rjkroege@chromium.org2014-06-0314-230/+244
| | | | | | | | | | | Patch 2 of 4 to specify the deviceSource of a desired fling animation request via enum throughout Blink and Chromium. BUG=343327 Review URL: https://codereview.chromium.org/304793003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274643 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-24 15:25:07 +0000