GitLab

In onAttachedToWindow, check that if the view is hardware accelerated,
then enable hardware accelerated 2d canvas. Similarly disable canvas on
detach.

Note that accelerated 2d canvas is still off by default, but this patch
adds a command line switch to turn it on.

BUG=332273

Review URL: https://codereview.chromium.org/140753006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245648 0039d316-1c4b-4281-b951-d872f2087c98

I should also write "end-to-end" data pipe tests ... but that will be a
nontrivial project.

R=sky@chromium.org

Review URL: https://codereview.chromium.org/130633005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245647 0039d316-1c4b-4281-b951-d872f2087c98

BUG=none

Review URL: https://codereview.chromium.org/141503002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245646 0039d316-1c4b-4281-b951-d872f2087c98

This defines WebScrollOffsetAnimationCurveImpl, which wraps a
cc::ScrollOffsetAnimationCurve. This is needed for
implementing the CSSOM Smooth Scroll API.

BUG=243871

Review URL: https://codereview.chromium.org/112933005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245645 0039d316-1c4b-4281-b951-d872f2087c98

BUG=333372

Review URL: https://codereview.chromium.org/135853023

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245644 0039d316-1c4b-4281-b951-d872f2087c98

BUG=225886
R=zelidrag@chromium.org

Review URL: https://codereview.chromium.org/130503010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245642 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245640 0039d316-1c4b-4281-b951-d872f2087c98

This is a prerequisiste for building GDB.

R=bradnelson@google.com

Review URL: https://codereview.chromium.org/131563007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245639 0039d316-1c4b-4281-b951-d872f2087c98

BUG=325581

Review URL: https://codereview.chromium.org/136923002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245638 0039d316-1c4b-4281-b951-d872f2087c98

These should be working now.

BUG=238735
NOTRY=true

Review URL: https://codereview.chromium.org/133613003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245637 0039d316-1c4b-4281-b951-d872f2087c98

Original CL: crrev.com/132733002
Reverted CL: crrev.com/135903002

TBR=samarth@chromium.org,sky@chromium.org
BUG=none

Review URL: https://codereview.chromium.org/137993020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245636 0039d316-1c4b-4281-b951-d872f2087c98

This patch does NOT prevent tap or long press when a touch move is consumed (see
crbug.com/327444).

An additional state is added to GestureState - GS_SYNTHETIC_CLICK_ABORTED. In addition,
the meaning of GS_PENDING_SYNTHETIC_CLICK_NO_SCROLL has changed.

GS_PENDING_SYNTHETIC_CLICK_NO_SCROLL indicates that one finger is down and no scrolling
can happen, but a tap or long press can still happen.

GS_SYNTHETIC_CLICK_ABORTED indicates that a finger is down, but no gestures can be
created until the number of active touch points changes.

BUG=333947

Review URL: https://codereview.chromium.org/133273013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245635 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245634 0039d316-1c4b-4281-b951-d872f2087c98

r1837: Support 'msvs_prebuild/msvs_postbuild' in MSBuild (VS 2010 and later)
r1838: win ninja: build fix for msvs_pre/postbuild error test
r1839: Fix VS 2008 generation with nested folders again
r1840: Strip the invalid characters from the string used as mspdbsrv endpoint

R=scottmg@chromium.org
BUG=335607

Review URL: https://codereview.chromium.org/141283007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245633 0039d316-1c4b-4281-b951-d872f2087c98

The oauth2 apis are handled by google_apis\gaia\gaia_oauth_client.

BUG=None

Review URL: https://codereview.chromium.org/139153011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245632 0039d316-1c4b-4281-b951-d872f2087c98

BUG=316637

Review URL: https://codereview.chromium.org/132033005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245631 0039d316-1c4b-4281-b951-d872f2087c98

This is a partial revert of https://codereview.chromium.org/120203003.
It is quite common for a page to generate multiple |DidStartLoading()|
notifications while it finishes loading.  Redundant notifications should
not reset a gesture mid-sequence.

BUG=335586

Review URL: https://codereview.chromium.org/141853002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245630 0039d316-1c4b-4281-b951-d872f2087c98

BUG=325380
NOTRY=true

Review URL: https://codereview.chromium.org/132983007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245629 0039d316-1c4b-4281-b951-d872f2087c98

Previously, updating bookmark bar could have cause page/devtools resize.
With new layout logic implemented in DevToolsController, resizing
page/devtools after everything else guarantees single resize operation.

BUG=331295

Review URL: https://codereview.chromium.org/131093004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245628 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245627 0039d316-1c4b-4281-b951-d872f2087c98

BUG=327528

Review URL: https://codereview.chromium.org/140123002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245626 0039d316-1c4b-4281-b951-d872f2087c98

NOTRY=true
BUG=335455
TBR=nduca

Review URL: https://codereview.chromium.org/131743023

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245625 0039d316-1c4b-4281-b951-d872f2087c98

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

Platform libraries may return non-null function pointers from dlsym or
getProcAddress for unsupported GL functions. Previously the function
binding logic tried to address this with a separate extension function
binding step, but since some of the bindings were still done without
consulting the extension string, this failed to account for some
conflicts between core and extension functions such as
glDiscardFramebufferEXT vs. glInvalidateFramebuffer.

Fix this by binding all functions that have multiple versions only after
the context has been made current, and consulting the extension and
version strings. The logic for binding each function is now only in one
place in the generated code and easy to follow.

The patch still does not guarantee that the function pointers would be
set to null if the function is unsupported. It only attempts to guarantee
that an incorrect version of a function is not bound in case another
version is supported. The patch is conservative like this to avoid
requiring the exact specification of binding conditions in case a function
only has one name, and to make it less likely to expose bugs elsewhere.

GetGLCoreProcAddress and GetGLProcAddress are combined into one function,
which always first looks for the function pointer with dlsym and then
with GetProcAddress. The new conditions for binding make sure that this
does not result in errors.

The patched bindings do not query for incorrect OES or ARB extension
strings without the GL_ prefix. Including the incorrect extension strings
without the prefix is assumed to have been a mistake. This applies to
OES_get_program_binary, OES_vertex_array_object, ARB_get_program_binary,
ARB_vertex_array_object, and APPLE_vertex_array_object.

BUG=322489
TEST=gpu_unittests, cc_unittests, WebGL conformance tests

Review URL: https://codereview.chromium.org/98643013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245623 0039d316-1c4b-4281-b951-d872f2087c98

BUG=134249

Review URL: https://codereview.chromium.org/141073003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245620 0039d316-1c4b-4281-b951-d872f2087c98

BUG=333499
TEST=none
R=oshima@chromium.org

Review URL: https://codereview.chromium.org/141873003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245619 0039d316-1c4b-4281-b951-d872f2087c98

BUG=333038

Review URL: https://codereview.chromium.org/133123006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245618 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245616 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=165318:165326&mode=html
TBR=
BUG=

Review URL: https://codereview.chromium.org/142003002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245615 0039d316-1c4b-4281-b951-d872f2087c98

We're experimenting with using values other than 0 or 1 to control coverage
granularity.

BUG=324216
TBR=glider@chromium.org

Review URL: https://codereview.chromium.org/130503011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245614 0039d316-1c4b-4281-b951-d872f2087c98

Before this, we fail create a main thread shared context if there are no
webviews in hardware initialized mode. The future plan is for
accelerated 2d canvas and webgl to use a shared context with the gpu
thread service, but keep inline video using the ui thread service.

Currently only video uses main thread context for webview, so for now,
only gate context creation for main video on having a
hardware-initalized webview. This makes turning on accelerated canvas
more convenient.

BUG=332146

Review URL: https://codereview.chromium.org/137443020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245613 0039d316-1c4b-4281-b951-d872f2087c98

This contains a stub Privet file system, behind a flag.

BUG=332182

Review URL: https://codereview.chromium.org/120533006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245612 0039d316-1c4b-4281-b951-d872f2087c98

Min granularity was still not being calculated right. Fix it again and add a unit test.

BUG=268300

Review URL: https://codereview.chromium.org/141883002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245611 0039d316-1c4b-4281-b951-d872f2087c98

The general rule is that touch editing handles should fade out when they
are dismissed, unless handles and text are moving relative to each
other. So, handles fade out except in following cases, in which they
disappear almost immediately (i.e. they fade out super quickly):
- When handle is dragged out of content view. In this case it should
  actually scroll the contents, but that's a separate issue (see
  crbug.com/269003);
- When starting touch scrolling or gesture navigation.

BUG=313561

Review URL: https://codereview.chromium.org/138033014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245610 0039d316-1c4b-4281-b951-d872f2087c98

Test that the proper languages and keyboards are displayed at OOBE for
each supported region.

BUG=327034
NOTRY=True

Review URL: https://codereview.chromium.org/137783008

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245609 0039d316-1c4b-4281-b951-d872f2087c98

Replaces a DCHECK with parse error when parsing a WebM
cluster that has no timecode. This supplements the existing
WebMClusterParser::OnBlock() logic that similarly indicates
parse error when processing blocks. However, if there were
no blocks in the cluster, then the DCHECK could have been
hit if there were no timecode.

R=acolwell@chromium.org
BUG=335344
TEST=(local Linux) All media_unittests pass including the new ones

Review URL: https://codereview.chromium.org/141013008

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245608 0039d316-1c4b-4281-b951-d872f2087c98

R=sky@chromium.org

Review URL: https://codereview.chromium.org/141973003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245607 0039d316-1c4b-4281-b951-d872f2087c98

Review URL: https://codereview.chromium.org/135903009

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245606 0039d316-1c4b-4281-b951-d872f2087c98

Don't hook up Init()/Shutdown() to our test harnesses yet, because
things blow up (we currently have singletons that will hold handles
across tests).

R=sky@chromium.org

Review URL: https://codereview.chromium.org/136793026

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245605 0039d316-1c4b-4281-b951-d872f2087c98

R=sky@chromium.org
BUG=121242
TEST=visual test

Review URL: https://codereview.chromium.org/132543003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245604 0039d316-1c4b-4281-b951-d872f2087c98