summaryrefslogtreecommitdiffstats
path: root/content/port
Commit message (Collapse)AuthorAgeFilesLines
* [Android] Remove unused RWHVA touch handler notificationjdduke@chromium.org2014-02-051-1/+0
| | | | | | | | | The RenderWidgetHostViewAndroid::HasTouchEventHandlers notification is no longer used, remove accordingly. Review URL: https://codereview.chromium.org/153953003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248900 0039d316-1c4b-4281-b951-d872f2087c98
* Start moving context menu code to RenderFrame.jam@chromium.org2014-01-311-1/+3
| | | | | | | | | | | The selection code will have to move as well. That will happen in future changes. BUG=304341 R=nasko@chromium.org Review URL: https://codereview.chromium.org/130773004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248091 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Perform eager gesture recognition on MotionEventsjdduke@chromium.org2014-01-301-1/+1
| | | | | | | | | | | | | | | | ContentViewGestureHandler conditionally forwards MotionEvent's to the Android gesture detection pipeline, depending on the current touch stream handling disposition. However, this approach is fragile, as the detection pipeline expects a consistent touch stream for each sequence. Instead, forward all MotionEvent's immediately for gesture detection, conditionally dispatching the generated gestures depending on the touch stream ack dispositions. BUG=295075,334040,327444,240550,234516 NOTRY=true Review URL: https://codereview.chromium.org/120513005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248066 0039d316-1c4b-4281-b951-d872f2087c98
* Support format using enum argument for Async readback.siva.gunturi@samsung.com2014-01-241-1/+1
| | | | | | | | | | As of now we are passing bool to detect the format like rgb565, but ideally the format itself should be passed. BUG=323150 Review URL: https://codereview.chromium.org/143683003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246888 0039d316-1c4b-4281-b951-d872f2087c98
* Fix INPUT_EVENT_ACK_STATE_MAX.tdresser@chromium.org2014-01-201-1/+1
| | | | | | | | BUG=None Review URL: https://codereview.chromium.org/140783010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245941 0039d316-1c4b-4281-b951-d872f2087c98
* content_gl_tests were failing because, we are checking for rgb565 platform ↵siva.gunturi@samsung.com2014-01-201-1/+2
| | | | | | | | | | | | | | | | | support on hardware and failing intentionally, which was not correct, the test should be skiped instead. This patch takes care of that along with the base patch. On Aura with Nvidiea drivers the support is not there, so the test fails previously now weare skipping it by displaying the reason. Android the support gets passed. BUG=323150 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245772 Review URL: https://codereview.chromium.org/133363004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245896 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 245772 "content_gl_tests were failing because, we are che..."kbr@chromium.org2014-01-181-2/+1
| | | | | | | | | | | | | | | | | | | | Caused assertion failures in content_gl_tests on all debug GPU bots. > content_gl_tests were failing because, we are checking for rgb565 platform support > on hardware and failing intentionally, which was not correct, the test should be skiped instead. This patch takes care of that along with the base patch. > On Aura with Nvidiea drivers the support is not there, so the test fails previously now weare skipping it by displaying the reason. > Android the support gets passed. > > > BUG=323150 > > Review URL: https://codereview.chromium.org/133363004 TBR=siva.gunturi@samsung.com Review URL: https://codereview.chromium.org/142413002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245790 0039d316-1c4b-4281-b951-d872f2087c98
* content_gl_tests were failing because, we are checking for rgb565 platform ↵siva.gunturi@samsung.com2014-01-181-1/+2
| | | | | | | | | | | | | | | support on hardware and failing intentionally, which was not correct, the test should be skiped instead. This patch takes care of that along with the base patch. On Aura with Nvidiea drivers the support is not there, so the test fails previously now weare skipping it by displaying the reason. Android the support gets passed. BUG=323150 Review URL: https://codereview.chromium.org/133363004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245772 0039d316-1c4b-4281-b951-d872f2087c98
* Let the browser know the end of flingwangxianzhu@chromium.org2014-01-171-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Android, resize event caused by showing/hiding top controls may be expensive and cause janky fling if it is sent before the end of fling. Let the browser know the end of fling so that the browser can delay the resize event. As we have not resolved the issue of raciness between the main thread and the compositor thread, and between the renderer process and the browser process, about the sequence of fling events and notifications, for now we don't use the notification to update the fling status in ContentViewGestureHandler and GestureEventFilter. The DidStopFlinging notification is sent along the following path: - Renderer side: - compositor-thread-flinging: InputHandlerProxy::CancelCurrentFling() -> InputHandlerWrapper::DidStopFlinging() -> InputHandlerManager::DidStopFlinging() -> InputEventFilter::DidStopFlinging() -> IPC::Sender::Send(ViewHostMsg_DidStopFlinging) - main-thread-flinging (existing except the steps same as compositor-thread-flinging): WebViewImpl::endActiveFlingAnimation() -> RenderWidgetCompositor::didStopFlinging() -> LayerTreeHost::didStopFlinging() -> ThreadProxy::MainThreadHasStoppedFlinging() -> LayerTreeHostImpl::MainThreadHasStoppedFlinging() -> InputHandlerProxy::MainThreadHasStoppedFlinging() then same as compositor-thread-flinging[1:] - Browser side: RenderWidgetHostImpl::OnMessageReceived(ViewHostMsg_DidStopFlinging) -> RenderWidgetHostImpl::OnFlingingStopped() // Android only. No-op on other platforms -> RenderWidgetHostViewAndroid::DidStopFlinging() -> ContentViewCoreImpl::DidStopFlinging() -> ContentViewCore.onNativeFlingStopped() // Java -> ContentViewClient.onFlingStopped() then downstream embedder code BUG=244736 Review URL: https://codereview.chromium.org/131373004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245624 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of Add RGB565 Texture readback support in gl_helper ↵ager@chromium.org2014-01-171-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | (https://codereview.chromium.org/88033002/) Reason for revert: content_gl_tests failing on multiple gpu bots on the chromium.webkit buildbot. Example: http://chromegw.corp.google.com/i/chromium.webkit/builders/GPU%20Mac10.7/builds/19123 Original issue's description: > Add RGB565 Texture readback support in gl_helper > > Plan is to add a RGB565 readback and copy conversion for RGBA8 to RGB565 in GLHelper. > > BUG=323150 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245431 TBR=dtrainor@chromium.org,sievers@chromium.org,hubbe@chromium.org,aelias@chromium.org,piman@chromium.org,siva.gunturi@samsung.com NOTREECHECKS=true NOTRY=true BUG=323150 Review URL: https://codereview.chromium.org/137783022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245477 0039d316-1c4b-4281-b951-d872f2087c98
* Add RGB565 Texture readback support in gl_helpersiva.gunturi@samsung.com2014-01-171-1/+2
| | | | | | | | | | Plan is to add a RGB565 readback and copy conversion for RGBA8 to RGB565 in GLHelper. BUG=323150 Review URL: https://codereview.chromium.org/88033002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245431 0039d316-1c4b-4281-b951-d872f2087c98
* Start using FocusedNodedChanged to restartInput.aurimas@chromium.org2014-01-161-0/+3
| | | | | | | | | | | | Android requires us to call restart input when input node changes. Previously we relied on onHandleGesture which is not the right way to do it. BUG=242715 Review URL: https://codereview.chromium.org/56643003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245130 0039d316-1c4b-4281-b951-d872f2087c98
* Remove some code inside USE_AURA and OS_WIN ifdefs in content.jam@chromium.org2014-01-141-5/+1
| | | | | | | | | | | I also removed the _win.cc files inside content. BUG=330735 R=scottmg@chromium.org Review URL: https://codereview.chromium.org/137403005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@244768 0039d316-1c4b-4281-b951-d872f2087c98
* Convert video capture pipline to base::TimeTickssheu@chromium.org2014-01-081-7/+5
| | | | | | | | | | | | | base::TimeTicks is a monotonic clock, unlike base::Time, which may change if the system time is changed. Switch over the video capture pipeline to use this clock. BUG=249215 TEST=local build, run on CrOS snow, desktop Linux Review URL: https://codereview.chromium.org/101843005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243493 0039d316-1c4b-4281-b951-d872f2087c98
* Process accessibility messages in RVHI rather than RWHV*.dmazzoni@chromium.org2013-12-311-2/+5
| | | | | | | | | BUG=none NOTRY=true Review URL: https://codereview.chromium.org/122563002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242753 0039d316-1c4b-4281-b951-d872f2087c98
* Remove LatencyInfo merge from software rendering pathmiletus@chromium.org2013-12-231-1/+1
| | | | | | | | | BUG=246034 TEST=unittests pass. Review URL: https://codereview.chromium.org/111483003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242404 0039d316-1c4b-4281-b951-d872f2087c98
* Remove code only used by Mac single threaded compositing.ccameron@chromium.org2013-12-171-3/+0
| | | | | | | | | | | | | | | | | | | Mac single threaded compositing is no longer a shipping configuration, so remove code added to throttle swap acks for the single threaded compositor path. The Mac single threaded path will still work, but will not have a throttled framerate anymore. This will become even less relevant as the Mac moves to a browser compositor. Pull out all code associated with AboutToWaitForBackingStoreMsg, since does nothing now. Also remove some dead function prototypes. BUG=286038 Review URL: https://codereview.chromium.org/116103002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@241225 0039d316-1c4b-4281-b951-d872f2087c98
* Keep the oldest LatencyInfo when coalescing input eventsmiletus@chromium.org2013-12-111-1/+6
| | | | | | | | | | | | | | | Input events can be coalesced at browser side, e.g. GestureScrollUpdate, before being sent to renderer. Currently when events are coalesced, LatencyInfo are merged. We want to move to per-event LatencyInfo tracking and get rid of LatencyInfo merge. It seems reasonable to keep the oldest LatencyInfo, which when used for input event latency analysis, will represent the longest latency. BUG=246034 TEST=None Review URL: https://codereview.chromium.org/86603003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240160 0039d316-1c4b-4281-b951-d872f2087c98
* Convert string16 to base::string16 in content.brettw@chromium.org2013-12-032-3/+3
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/102593002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238447 0039d316-1c4b-4281-b951-d872f2087c98
* Fix windowless NPAPI Flash videos not working on certain sites.ananta@chromium.org2013-11-261-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a continuation of the previous patch https://codereview.chromium.org/69953030 which addressed this on some sites. We intercepted the WindowFromPoint API in that patch and returned the handle to the dummy plugin window. There was a bug in the WindowFromPoint patch which was returning the first available child window in the parent window hierarchy. We need to invoke the ChildWindowFromPoint API to get the actual child window and return it if it is the dummy window. The other changes are as below:- 1. The RenderWidgetHostViewAura class was not destroying the dummy window when the instance was destroyed. 2. When the RenderWidgetHostViewAura class is hidden due to the user switching to another tab, we set the bounds of the hidden window to 0. When the RenderWidgetHostViewAura instance is shown we restore the bounds of the hidden window. This is to ensure that the ChildWindowFromPoint function used in the plugin process returns the correct HWND. 3. When the RenderWidgetHostViewAura instance is added to a root window we need to reparent the dummy plugin window to the new window. This magic happens in the RenderWidgetHostImpl::ParentChanged function. Previously we were reparenting the dummy windows in the plugin process. With the dummy plugin window in the browser hierarchy we only need to reparent this window to the new browser window. 4. We have a new method GetPluginViewId in the RenderWidgetHostViewPort interface for Aura Windows. This returns the dummy plugin parent window. Fixes bug https://code.google.com/p/chromium/issues/detail?id=301548 BUG=301548 R=cpu@chromium.org, jam@chromium.org, jam Review URL: https://codereview.chromium.org/83633007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237193 0039d316-1c4b-4281-b951-d872f2087c98
* Make VibrationMessageFilter available to other platforms.sl.ostapenko@samsung.com2013-11-251-0/+23
| | | | | | | | | | | Adds VibrationProvider interface that simplifies adding vibration API handlers for other platforms and moves Android implementation into VibrationProviderAndroid. Also adds ContentBrowserClient::OverrideVibrationProvider() method that allows embedder application override handling of blink Vibration API. BUG=222504 Review URL: https://codereview.chromium.org/23496051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237101 0039d316-1c4b-4281-b951-d872f2087c98
* Replace old with new synthetic gesture framework.dominikg@chromium.org2013-11-212-47/+0
| | | | | | | | | | | | | | | | | - Remove current implementation of synthetic gestures. - Rename temporarily named classes and files of new synthetic gesture framework (e.g. SyntheticGestureNew -> SyntheticGesture). - Link up new implementation in browser and renderer. - Hook up synthetic gesture controller to input flushing in RWHI. - Update JavaScript front-end and Telemetry. BUG=297980 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=236254 Review URL: https://codereview.chromium.org/62443007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236545 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 236254 "Replace old with new synthetic gesture framework."rch@chromium.org2013-11-202-0/+47
| | | | | | | | | | | | | | | | | | | | | > Replace old with new synthetic gesture framework. > > - Remove current implementation of synthetic gestures. > - Rename temporarily named classes and files of new synthetic gesture framework > (e.g. SyntheticGestureNew -> SyntheticGesture). > - Link up new implementation in browser and renderer. > - Hook up synthetic gesture controller to input flushing in RWHI. > - Update JavaScript front-end and Telemetry. > > BUG=297980 > > Review URL: https://codereview.chromium.org/62443007 TBR=dominikg@chromium.org Review URL: https://codereview.chromium.org/79143002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236264 0039d316-1c4b-4281-b951-d872f2087c98
* Replace old with new synthetic gesture framework.dominikg@chromium.org2013-11-202-47/+0
| | | | | | | | | | | | | | | - Remove current implementation of synthetic gestures. - Rename temporarily named classes and files of new synthetic gesture framework (e.g. SyntheticGestureNew -> SyntheticGesture). - Link up new implementation in browser and renderer. - Hook up synthetic gesture controller to input flushing in RWHI. - Update JavaScript front-end and Telemetry. BUG=297980 Review URL: https://codereview.chromium.org/62443007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236254 0039d316-1c4b-4281-b951-d872f2087c98
* Events ignoring ack disposition receive synthetic acks.tdresser@chromium.org2013-11-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Previously committed (https://codereview.chromium.org/44983003/), and then reverted (https://codereview.chromium.org/66283005) Can't reproduce test failures locally or on the trybots, so we'll try committing again. Logic to handle events which ignore ack disposition has moved from the |GestureEventFilter| to the |ImmediateInputRouter|, and |WebInputEventTraits|. This will allow us to make more events ignore their ack disposition, including touch events. Gesture event types which will eventually ignore their ack disposition include Tap, ScrollBegin, PinchBegin, PinchEnd, etc. BUG=302852, 275611 TEST=ImmediateInputRouterTest.EventsIgnoringAckDispositionDontWaitForAcks, ImmediateInputRouterTest.EventsIgnoringAckDispositionStayInOrder TBR=jdduke@, joi@ Review URL: https://codereview.chromium.org/71073003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234866 0039d316-1c4b-4281-b951-d872f2087c98
* SyntheticGestureTarget implementation for injecting synthetic input events.kouhei@chromium.org2013-11-121-0/+6
| | | | | | | | | | | This will be used from SyntheticGesture implementations such as SyntheticSmoothScrollGesture(New) to inject input events in a Android/aura specific way. The patch also includes fallback implementation in SyntheticGetsureTargetBase which passes the input events to RWH. BUG=297960 BUG=306459 Review URL: https://codereview.chromium.org/26664002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234354 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 233946 "Events ignoring ack disposition receive synthetic..."rockot@google.com2013-11-081-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | android test failures http://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/16097 > Events ignoring ack disposition receive synthetic acks. > > Logic to handle events which ignore ack disposition has moved from the > |GestureEventFilter| to the |ImmediateInputRouter|, and |WebInputEventTraits|. > > This will allow us to make more events ignore their ack disposition, including > touch events. > > Gesture event types which will eventually ignore their ack disposition include > Tap, ScrollBegin, PinchBegin, PinchEnd, etc. > > BUG=302852,275611 > TEST=ImmediateInputRouterTest.EventsIgnoringAckDispositionDontWaitForAcks, > ImmediateInputRouterTest.EventsIgnoringAckDispositionStayInOrder > > Review URL: https://codereview.chromium.org/44983003 TBR=tdresser@chromium.org Review URL: https://codereview.chromium.org/66283005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233962 0039d316-1c4b-4281-b951-d872f2087c98
* Events ignoring ack disposition receive synthetic acks.tdresser@chromium.org2013-11-081-0/+1
| | | | | | | | | | | | | | | | | | | Logic to handle events which ignore ack disposition has moved from the |GestureEventFilter| to the |ImmediateInputRouter|, and |WebInputEventTraits|. This will allow us to make more events ignore their ack disposition, including touch events. Gesture event types which will eventually ignore their ack disposition include Tap, ScrollBegin, PinchBegin, PinchEnd, etc. BUG=302852,275611 TEST=ImmediateInputRouterTest.EventsIgnoringAckDispositionDontWaitForAcks, ImmediateInputRouterTest.EventsIgnoringAckDispositionStayInOrder Review URL: https://codereview.chromium.org/44983003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233946 0039d316-1c4b-4281-b951-d872f2087c98
* Warm up the GPU when the user touches the screenskyostil@chromium.org2013-11-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | Some devices perform very aggressive GPU power management. This is good for battery life, but can lead long delays when the GPU is woken up after having been idle. As an example, on Nexus 4 the additional delay from spinning up the GPU is on the order of 10 ms. This can easily cause us to miss the next vsync when responding to an input event. This patch adds a mechanism for GPU process clients to notify ahead of time that they are likely to draw very soon and the GPU should be warmed up. We drive this signal with the TapDown gesture, which is sent whenever the user starts touching the display. This fits well to the common scrolling scenario where the TapDown is sent several tens of milliseconds before the first ScrollBy event that actually causes rendering. BUG=309734 Review URL: https://codereview.chromium.org/49623002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233889 0039d316-1c4b-4281-b951-d872f2087c98
* Rename WebKit namespace to blink (part 3)abarth@chromium.org2013-11-073-14/+14
| | | | | | | | | | | This CL updates all references to the WebKit namespace in content. TBR=darin@chromium.org BUG=295096 Review URL: https://codereview.chromium.org/63253002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233513 0039d316-1c4b-4281-b951-d872f2087c98
* Consolidate WebInputEvent coalescing logicjdduke@chromium.org2013-10-161-0/+12
| | | | | | | | | | | | Code for coalescing the various WebInputEvent types is littered throughout the code. Move all such logic into WebInputEventTraits, making possible standalone test for event coalescing, and simplifying code that relies on coalescing. BUG=303238 Review URL: https://codereview.chromium.org/26923002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228828 0039d316-1c4b-4281-b951-d872f2087c98
* Move surface resize platform code from GpuProcessHostUIShim to ↵sl.ostapenko@samsung.com2013-10-151-0/+3
| | | | | | | | | | RenderWidgetHostView implementations. BUG=303425 Review URL: https://codereview.chromium.org/25795002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228785 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 227058 "Move surface resize platform code from GpuProcess..."enne@chromium.org2013-10-041-3/+0
| | | | | | | | | | | | | | | | | This was causing a compile failure for Windows Blink bots. http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win%20Builder/builds/43979/steps/compile/logs/stdio > Move surface resize platform code from GpuProcessHostUIShim to RenderWidgetHostView implementations. > > BUG=303425 > > Review URL: https://codereview.chromium.org/25795002 TBR=sl.ostapenko@samsung.com Review URL: https://codereview.chromium.org/26015005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227106 0039d316-1c4b-4281-b951-d872f2087c98
* Move surface resize platform code from GpuProcessHostUIShim to ↵sl.ostapenko@samsung.com2013-10-041-0/+3
| | | | | | | | | | RenderWidgetHostView implementations. BUG=303425 Review URL: https://codereview.chromium.org/25795002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227058 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Provide synchronized input flush with BeginFramejdduke@chromium.org2013-09-261-0/+7
| | | | | | | | | | | | | The BufferedInputRouter relies on periodic flush signals. Provide hooks for such flush requests and signals via the RenderWidgetHostView, and wire this to BeginFrame messages on Android. Expose the functionality behind the --enable-buffered-input-router flag. BUG=245499,264869 Review URL: https://codereview.chromium.org/23983036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225387 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Revert 224496 "Move ui/base/latency_info* to ui/events""ben@chromium.org2013-09-231-1/+1
| | | | | | | | | | | | | This reverts commit d1ec3f7f30d07132bf0f75e4938d50a508bc7637. Attempt at re-landing this previous change. Moves LatencyInfo from ui/base to ui/events. TBR=sky@chromium.org,jamesr@chromium.org,jschuh@chromium.org BUG=none Review URL: https://codereview.chromium.org/24257011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224769 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 224496 "Move ui/base/latency_info* to ui/events"ben@chromium.org2013-09-201-1/+1
| | | | | | | | | | | | | | | | | | > Move ui/base/latency_info* to ui/events > > Latest in a sequence of changes to extract ui/gfx as its own component and sever ties on ui/base from various should-be-lower-level components. > > TBR=jamesr@chromium.org, sky@chromium.org > > BUG=none > > Review URL: https://codereview.chromium.org/23464099 TBR=ben@chromium.org Review URL: https://codereview.chromium.org/24141009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224503 0039d316-1c4b-4281-b951-d872f2087c98
* Move ui/base/latency_info* to ui/eventsben@chromium.org2013-09-201-1/+1
| | | | | | | | | | | | Latest in a sequence of changes to extract ui/gfx as its own component and sever ties on ui/base from various should-be-lower-level components. TBR=jamesr@chromium.org, sky@chromium.org BUG=none Review URL: https://codereview.chromium.org/23464099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224496 0039d316-1c4b-4281-b951-d872f2087c98
* Synthetic pinch-to-zoom gesture.dominikg@chromium.org2013-09-121-0/+5
| | | | | | | | | | | | | | | | Add implementation of synthetic pinch-to-zoom gesture, exposed in JavaScript through chrome.gpuBenchmarking.pinchBy(). A pinch gesture is defined by four parameters: 1) whether to zoom in or out, 2) the number of pixels to cover during the gesture, 3,4) the x/y coordinates of the anchor point of the gesture. BUG=264810 Review URL: https://chromiumcodereview.appspot.com/23587002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222696 0039d316-1c4b-4281-b951-d872f2087c98
* Add InputEvent and EventPacket types for batched input deliveryjdduke@chromium.org2013-09-071-0/+1
| | | | | | | | | | | | | With the BufferedInputRouter, browser input events will be batched into packets before being sent to the renderer. Add a common InputEvent type that provides id'ed carriage of either WebInputEvents or general IPC input messages. Also add a composite EventPacket type for batched InputEvent transport and dispatch. BUG=245499 Review URL: https://chromiumcodereview.appspot.com/19624005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221905 0039d316-1c4b-4281-b951-d872f2087c98
* Move Range code to gfx.ben@chromium.org2013-09-061-3/+3
| | | | | | | | | | | Part of a set of changes to fix the circular dependency between ui/base and ui/gfx, with the aim of making gfx its own component. R=jam@chromium.org, jschuh@chromium.org, rsesek@chromium.org BUG=285385,103304 Review URL: https://codereview.chromium.org/24012002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221762 0039d316-1c4b-4281-b951-d872f2087c98
* Use Blink accessibility enums in Chromiumdmazzoni@chromium.org2013-09-041-3/+3
| | | | | | | | | | | | | | | | | | | | This is a refactoring-only change! Eliminates enums for accessibility roles, states, and notifications and uses equivalent enums from Blink instead. Saves several giant switch statements, saves a few characters per line, and makes future changes to roles and states simpler. Another benefit is that you can search for a role, state, or event and find all of the places where it's used throughout the code at once. Also renames WebAccessibilityObject -> WebAXObject and notification -> event in the context of accessibility. BUG=269034 Review URL: https://chromiumcodereview.appspot.com/23651003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221295 0039d316-1c4b-4281-b951-d872f2087c98
* reorder RenderWidgetHostViewPort::TextInputTypeChanged argumentyoichio@chromium.org2013-09-041-2/+2
| | | | | | | | | | This CL is to intent that we have two different fields that represent input field attributes. BUG=244688 Review URL: https://chromiumcodereview.appspot.com/23604019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221128 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor synthetic gesture handling to prepare for more gestures.dominikg@chromium.org2013-08-232-10/+10
| | | | | | | | | | | | | | | | | | Currently there's only one gesture, smooth scroll. This patch provides changes that will make it easier to add new gestures. Functionality that's independent of scrolling has been renamed to SyntheticGesture*. Since many touch gestures are variations of touch-drag (with one or more pointers) this patch introduces a new GenericTouchGesture Java class to simulate all of these gestures. Currently, it only supports a single pointer, but it can be easily extented to support more. The smooth scroll gesture uses this class for the Android implementation. BUG=264810 Review URL: https://chromiumcodereview.appspot.com/22883004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219280 0039d316-1c4b-4281-b951-d872f2087c98
* Handle root layer fling Java-side in android_webview.mkosiba@chromium.org2013-08-021-1/+2
| | | | | | | | | | | | | | The android_webview implementation needs to handle root layer fling Java-side. This is required for proper integration with the android view system which requires the fling scroll offset update to be performed as a result of the computeScroll method. BUG=None TEST=AndroidWebViewTest Review URL: https://chromiumcodereview.appspot.com/20990009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215339 0039d316-1c4b-4281-b951-d872f2087c98
* Update include paths in miscellaneous content/ directories for base/process ↵rsesek@chromium.org2013-07-251-1/+1
| | | | | | | | | | | changes. BUG=242290 TBR=avi@chromium.org Review URL: https://codereview.chromium.org/20114003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213619 0039d316-1c4b-4281-b951-d872f2087c98
* Move NPAPI implementation out of webkit/plugins/npapi and into content.jam@chromium.org2013-07-191-7/+2
| | | | | | | | | | | | | | | | Notes: -gtk_plugin_container_manager* and gtk_plugin_container* move to content/browser/renderer_host/ since that's all where they're used -plugin_list* and plugin_constants_win* move to content/common as they're used by child processes and the browser -webplugin_impl* and webplugin_page_delegate.h move to content/renderer as that's where they're used. I will remove webplugin_page_delegate.h in a followup change as it's no longer needed. -the rest moves to content/child/npapi -a few constants moved from plugin_constants_win.h to plugin_util.h temporarily BUG=237249 TBR=scottmg Review URL: https://codereview.chromium.org/19761007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212485 0039d316-1c4b-4281-b951-d872f2087c98
* Associate an id with the output surface to handle lost contextspiman@chromium.org2013-07-181-1/+3
| | | | | | | | | | | This lets us cull acks that were meant for a previous output surface, so that we don't try to return/release resources that have been destroyed already. BUG=239931 Review URL: https://chromiumcodereview.appspot.com/19331002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212470 0039d316-1c4b-4281-b951-d872f2087c98
* Move WebMenuItem to content::MenuItem.darin@chromium.org2013-07-171-3/+2
| | | | | | | | BUG=237267 Review URL: https://chromiumcodereview.appspot.com/19393003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211982 0039d316-1c4b-4281-b951-d872f2087c98
* Add new parameter ui::TextInputMode to ViewHostMsg_TextInputTypeChanged IPC ↵yoichio@chromium.org2013-07-111-1/+3
| | | | | | | | | | | | | | | | | | | | message. Focused input element has new attribute inputmode, which tells browser to switch character type like "latin", "katakana". at RenderWidget::UpdateTextInputType(), 1. get WebKit::WebTextInputInfo, which has inputmode as WebString. 2. convert it to corresponding enum ui::TextInputMode this cl adds. 3. set it to IPC parameter extended. BUG=244758 Review URL: https://chromiumcodereview.appspot.com/18682002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211064 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-11 03:14:39 +0000