1. 19 Aug, 2020 33 commits
  2. 18 Aug, 2020 7 commits
    • Tommy Li's avatar
      [omnibox] ZeroSuggestProvider::TypeOfResultToRun w/ AutocompleteInput · 26a9f582
      Tommy Li authored
      This CL refactors ZeroSuggestProvider::TypeOfResultToRun to take an
      AutocompleteInput as a parameter instead of just the current page URL.
      
      We need this because differentiating the on-focus vs. on-clobber
      ZeroSuggest modes requires access to AutocompleteInput::focus_type().
      
      This CL also makes the method 'static', for three reasons:
      
       1. The function is more easily testable when it only depends on its
          parameters, rather than any state in the member variables.
      
       2. The member variables store data that's also in the |input|
          parameter, and I didn't want to introduce ambiguity as to which
          is used.
      
       3. We plan to split MostVisited into its own provider, and we will
          want to share some logic from TypeOfResultToRun. Making this
          method static is a step towards that future.
      
      For reviewability, this CL actually has no functional changes, and
      just moves things around.
      
      The followup CL will actually add the on-clobber vs. on-focus logic to
      TypeOfResultToRun.
      
      Bug: 1106096
      Change-Id: I69c8f2f08a182796be9ce1c66611fe6788a6158a
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360562Reviewed-by: default avatarTomasz Wiszkowski <ender@google.com>
      Commit-Queue: Tommy Li <tommycli@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799394}
      26a9f582
    • Steven Bennetts's avatar
      CrOS: Do not set an empty policy hostname · 1c0816a5
      Steven Bennetts authored
      This is in preparation for adding UI to allow users
      to set a custom DHCP hostname. Currently the policy
      code is always setting the hostname, even if
      kDeviceHostnameTemplate is not set by policy,
      which overrides any other custom set hostname.
      
      Bug: 1103272
      Change-Id: Ia99ee58c59ae1f38e8fe10ed693997dead861c4b
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320991
      Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
      Reviewed-by: default avatarKyle Horimoto <khorimoto@chromium.org>
      Reviewed-by: default avatarOmar Morsi <omorsi@google.com>
      Reviewed-by: default avatarDenis Kuznetsov [CET] <antrim@chromium.org>
      Reviewed-by: default avatarRoman Sorokin [CET] <rsorokin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799393}
      1c0816a5
    • Sammie Quon's avatar
      dark mode: Flip base colors for ink drop. · 64f8e172
      Sammie Quon authored
      Original thought the dark ripple was for the dark background.
      
      Test: manual
      Bug: 1117203
      Change-Id: I3221271f8bb1d1d32a8832c75a46c0b8f726426e
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363997Reviewed-by: default avatarXiyuan Xia <xiyuan@chromium.org>
      Commit-Queue: Sammie Quon <sammiequon@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799392}
      64f8e172
    • John Palmer's avatar
      Change spacing for undo window · c3ee7e10
      John Palmer authored
      Should be 8px, old number worked out to 16px
      
      BUG=1117379
      
      Change-Id: Ic6cef89a6c9b93fab24b538f13d6c07fa4f06647
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362062
      Auto-Submit: John Palmer <jopalmer@chromium.org>
      Commit-Queue: Keith Lee <keithlee@chromium.org>
      Reviewed-by: default avatarKeith Lee <keithlee@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799391}
      c3ee7e10
    • David Bokan's avatar
      Cleanup FakeLayerTreeHost's initialization of Impl · 613ec9bd
      David Bokan authored
      As part of splitting out input from LayerTreeHostImpl I found some
      issues in tests that use FakeLayerTreeHost. This class also initializes
      a FakeLayerTreeHostImpl which is used in some tests.
      
      However, some tests also call InitializeSingleThreaded to use the
      FakeLayerTreeHost with a Proxy. Initializing a Proxy will call
      LayerTreeHost::CreateLayerTreeHostImpl which currently creates a (real)
      LayerTreeHostImpl that's owned by the Proxy. These tests are incorrectly
      running with multiple LTHI objects.
      
      This CL overrides CreateLayerTreeHostImpl in the fake so that this
      method creates a fake Impl object. We also avoid manually creating a
      fake Impl inside the FakeLayerTreeHost and instead rely on the call
      to CreateLayerTreeHostImpl to store a pointer to the fake impl.
      
      For tests that don't use a Proxy, we now manually call a new
      CreateFakeLayerTreeHostImpl method that does the same thing and the
      FakeLayerTreeHost takes ownership of the Impl instead.
      
      Bug: 915926
      Change-Id: I63202e1717d2eab026688d69c8d0ef75939c7c47
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363247Reviewed-by: default avatarXianzhu Wang <wangxianzhu@chromium.org>
      Commit-Queue: David Bokan <bokan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799390}
      613ec9bd
    • Miguel Casas's avatar
      media/VaapiVideoDecoder: refactor failures UMA · 993d2e9e
      Miguel Casas authored
      ToT VaapiWrapper has a simple report-to-uma callback that clients have
      to implement and that usually just points to "error happened" in either
      the normal or the Vpp VaapiWrapper.
      
      This CL changes that:
      - VaapiWrapper provides a function for this: ReportVaapiErrorToUMA().
      - Clients bind their histogram (eg. Media.VaapiVideoDecoder.VAAPIError)
      to that new ReportVaapiErrorToUMA() method.
      - A new VaapiFunctions enumeration (with a matching UMA enum) is added
      to vaapi_wrapper.cc to identify which concrete vaBla() function failed,
      and is logged to UMA.
      
      This forces ToT UMA histograms (and associated enums) to be marked as
      obsolete, namely:
      -Media.VAJDA.DecoderFailure
      -Media.VAJDA.VppFailure
      -Media.VAJDAWorker.DecoderFailure
      -Media.VAJEA.VppFailure
      -Media.VAVDA.DecoderFailure
      -Media.VAVEA.EncoderFailure
      
      New ones are landed instead (with associated VaapiFunctions enum):
      -Media.VaapiImageDecodeAcceleratorWorker.VAAPIError
      -Media.VaapiJpegEncodeAccelerator.VAAPIError
      -Media.VaapiJpegEncodeAccelerator.VAAPIVppError
      -Media.VaapiMjpegDecodeAccelerator.VAAPIError
      -Media.VaapiMjpegDecodeAccelerator.VAAPIVppError
      -Media.VaapiVideoDecodeAccelerator.VAAPIError
      -Media.VaapiVideoDecoder.VAAPIError
      -Media.VaapiVideoEncodeAccelerator.VAAPIError
      -Media.VaapiVideoEncodeAccelerator.VAAPIVppError
      
      This CL also adds two new boolean histograms for VaapiVideoDecoder,
      who had none.
      
      Bug: b:162962069
      Change-Id: I561e48183f61de86247598fea4f3b10cd590c2e0
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339787
      Commit-Queue: Miguel Casas <mcasas@chromium.org>
      Reviewed-by: default avatarSteven Holte <holte@chromium.org>
      Reviewed-by: default avatarJao-ke Chin-Lee <jchinlee@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#799389}
      993d2e9e
    • Becca Hughes's avatar
      Make content attributes optional · 5b4d8221
      Becca Hughes authored
      For normal images contentAttributes are optional in
      the spec but the converter requires them. This makes
      them optional.
      
      Change-Id: I4073de51009e6e7802667b2d79a7ad485d939978
      Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363477
      Auto-Submit: Becca Hughes <beccahughes@chromium.org>
      Commit-Queue: Sam Bowen <sgbowen@google.com>
      Reviewed-by: default avatarSam Bowen <sgbowen@google.com>
      Cr-Commit-Position: refs/heads/master@{#799388}
      5b4d8221