GitLab

We are adding COMPONENT/TEAM information into OWNERS file(
views, etc).

Proposal to add TEAM/COMPONENT information into OWNERS files
http://bit.ly/add-team-component-proposal
Proposal about how to get suggested component for directory.
http://bit.ly/directory-mapping-proposal
TEAM-COMPONENT mapping
http://bit.ly/component-team-mapping

Additional Information:
Component lists
https://bugs.chromium.org/p/chromium/adminComponents

BUG=679905
R=msw@chromium.org

Review-Url: https://codereview.chromium.org/2740203004
Cr-Commit-Position: refs/heads/master@{#456244}

BUG=684609

Review-Url: https://codereview.chromium.org/2743843002
Cr-Commit-Position: refs/heads/master@{#456243}

Remove GpuMsg_Finalize, and associated code (e.g.
GpuProcessHost*::StopGpuProcess()). Introduce GpuService::Stop() mojom
api in its place, and content::StopGpuProcess() so that content embedders
(e.g. chromecast) can stop the gpu process when desired.

BUG=639941, 643746
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2723363002
Cr-Commit-Position: refs/heads/master@{#456242}

This test has syntax error and is missed in gn build file when added.

Review-Url: https://codereview.chromium.org/2738983006
Cr-Commit-Position: refs/heads/master@{#456241}

Currently, all external clients of SpellCheckRequest use it in only
one way -- pass it to SpellCheckRequester::requestCheckingFor
directly.

Hence, this patch makes the clients call the function directly without
knowing about details of this class, to reduce exposure of implementation
details.

BUG=n/a
TEST=n/a; no behavior changes

Review-Url: https://codereview.chromium.org/2740603003
Cr-Commit-Position: refs/heads/master@{#456240}

R=rdevlin.cronin@chromium.org
BUG=700312
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2745733004
Cr-Commit-Position: refs/heads/master@{#456239}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/aa4354795733..5cdfbfc97459

$ git log aa4354795..5cdfbfc97 --date=short --no-merges --format='%ad %ae %s'
2017-03-10 benjhayden Hide the InteractionTrack when only 1 UE.

Created with:
  roll-dep src/third_party/catapult

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2741803006
Cr-Commit-Position: refs/heads/master@{#456238}

BUG=680578

Review-Url: https://codereview.chromium.org/2713003003
Cr-Commit-Position: refs/heads/master@{#456237}

BUG=695952
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2733953008
Cr-Commit-Position: refs/heads/master@{#456236}

Keeping DisplaySnapshotMojo in display/types enables tighter use of
DEPS in ozone/platform/drm so relocate it appropriately.

BUG=620927

Review-Url: https://codereview.chromium.org/2738043004
Cr-Commit-Position: refs/heads/master@{#456235}

When associating bookmarks, sync nodes are matched to BookmarkNodes.
To match a BookmarkNode with a sync node, a BookmarkNodeFinder is
created and asked to find the child node with the matching title. When searching
for the title, BookmarkNodeFinder returns the first matching child in
its child_nodes_ map. This map is an unordered_map with undefined
iteration order. If sync node siblings share a title, the
BookmarkNodeFinder can erroneously swap their respective
BookmarkNodes.
To fix this, this CL makes the iteration order defined with
std::multimap, which stores pairs in insertion order.
This is safe since sync nodes are processed in the same
order as BookmarkNodes are stored.

R=skym@chromium.org
BUG=

Review-Url: https://codereview.chromium.org/2743713005
Cr-Commit-Position: refs/heads/master@{#456234}

FROM_CHROME_UI results in animations that we do not want and
FROM_EXTERNAL_APP allows the NTP to be closed if you hit back,
which I think is nice since we are creating a tab without any
user gesture so making it discardable seems correct.

BUG=695306

Review-Url: https://codereview.chromium.org/2742783004
Cr-Commit-Position: refs/heads/master@{#456233}

Revert of evaluating clipboard event target acording to w3c specification (patchset #7 id:120001 of https://codereview.chromium.org/2685723005/ )

Reason for revert:
Changing this functionality improved spec conformance, but introduced regressions where text that used to be copied is no longer copied:
crbug.com/695568
crbug.com/700163

A proposal to change the spec was made here:
https://github.com/w3c/clipboard-apis/issues/40

Original issue's description:
> Make Editor::findEventTargetFrom() to align Clipboard API specification
>
> This patch changes |Editor::findEventTargetFrom()| to return focused element if
> selection start is not editable to align Clipboard API specification[1] for
> improving interoperability.
>
> [1] https://w3c.github.io/clipboard-apis/#to-fire-a-clipboard-event
>
> BUG=690104
> TEST=webkit_unittests --gtest_filter=ClipboardEventFlowTest.*
>
> Review-Url: https://codereview.chromium.org/2685723005
> Cr-Commit-Position: refs/heads/master@{#451716}
> Committed: https://chromium.googlesource.com/chromium/src/+/7afbab0f7619c89aa7a5896024d1628a59cc0ef1

TBR=tkent@chromium.org,ojan@chromium.org,yosin@chromium.org,yutak@chromium.org,sigbjornf@opera.com,mwrobel@opera.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=690104

Review-Url: https://codereview.chromium.org/2745813002
Cr-Commit-Position: refs/heads/master@{#456232}

This is follow up cleanup after renaming NavigationHandle::IsSamePage to
NavigationHandle::IsSameDocument in this CL:
https://codereview.chromium.org/2716493004/

BUG=695189
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2742923002
Cr-Commit-Position: refs/heads/master@{#456231}

cros-disks's Unmount method now ignores the "force" option (CL:388592,
chromium:646224). This CL updates CrosDisksClient to stop passing the
"force" option when invoking the Unmount method.

BUG=700548
TEST=chromos_unittests

Review-Url: https://codereview.chromium.org/2743113003
Cr-Commit-Position: refs/heads/master@{#456230}

Added missing files.

BUG=none
R=jochen@chromium.org, thakis@chromium.org

Review-Url: https://codereview.chromium.org/2747483002
Cr-Commit-Position: refs/heads/master@{#456229}

This makes it easier/cleaner to implement CoreOobeView::Delegate on ScreenManager in a follow-up CL.

BUG=672142

Review-Url: https://codereview.chromium.org/2739073002
Cr-Commit-Position: refs/heads/master@{#456228}

This uses auto convert script to convert content instrumentation tests to JUnit4,
assisted with some manual clean up. For more on JUnit4 migration, check
src/testing/android/docs/junit4.md

BUG=640116

Review-Url: https://codereview.chromium.org/2708243004
Cr-Commit-Position: refs/heads/master@{#456227}

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

BUG=683729

Review-Url: https://codereview.chromium.org/2741783006
Cr-Commit-Position: refs/heads/master@{#456226}

CUPS provides cupsGetJobs2 but it doesn't provide the necessary fields
to report status accurately.  Notably, it doesn't provide
job-impressions-completed or printer-state-reasons both of which are
necessary to differentiate errors.

BUG=684853

Review-Url: https://codereview.chromium.org/2691093006
Cr-Commit-Position: refs/heads/master@{#456225}

This CL fixes an issue where Chrome would display a banner saying that it
was not the default browser when it actually was.

The cause of this was 'xdg-settings check default-web-browser
google-chrome.desktop' returning 'no' when Chrome might have been the
default (see further explanation in the CL comments).

BUG=578888
R=thestig@chromium.org

Review-Url: https://codereview.chromium.org/2737283002
Cr-Commit-Position: refs/heads/master@{#456224}

BUG=699287
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2742103002
Cr-Commit-Position: refs/heads/master@{#456223}

This exercises the is_cast_audio_only=true and enable_webrtc=false
codepaths which periodically break because they are not built.

Corresponding CL at https://chromium-review.googlesource.com/c/452802/

BUG=667546
TEST=`gn gen out_audio/ --args='is_chromecast=true
is_cast_audio_only=true enable_webrtc=false' && ninja -C out_audio/
cast_shell`

Review-Url: https://codereview.chromium.org/2538883003
Cr-Commit-Position: refs/heads/master@{#456222}

See bug for details of regression.

This reverts commit be0cfa14 which was:

Make Crashpad start asynchronous, and move back to chrome_elf

Crashpad initialization has been reworked to support an asynchronous
mode where StartHandler() only calls CreateThread() and does not
synchronize with that thread, making it safe to use in DllMain().

So, we can now move it back into chrome_elf to catch earlier crashes.

We block much later now in browser startup, before a renderer (i.e.
another client that would connect to the handler) will be started. This
should not be strictly necessary, but is slightly more conservative as a
first pass. This allows for error reporting, and prevents log spew from
each renderer that starts up and tries to connect to a nonexistent
handler. Also added is a UMA timer to see how long we're blocking
startup for by joining with the background thread.

TBR=mark@chromium.org, thestig@chromium.org, grt@chromium.org
BUG=700371

Review-Url: https://codereview.chromium.org/2743923003
Cr-Commit-Position: refs/heads/master@{#456221}

BUG=674667

Review-Url: https://codereview.chromium.org/2734963002
Cr-Commit-Position: refs/heads/master@{#456220}

This change emits a UKM PageLoad metric for the EffectiveConnectionType
observed at navigation start.

This change also corrects an issue where we logged some information in
OnStart. When OnStart is invoked, we don't yet know if we're observing
a page load, so we move all logging to later in the flow, when we know
we're observing a page load.

BUG=700537

Review-Url: https://codereview.chromium.org/2740403002
Cr-Commit-Position: refs/heads/master@{#456219}

BUG=675285

Review-Url: https://codereview.chromium.org/2745893002
Cr-Commit-Position: refs/heads/master@{#456218}

Update waterfall testing config for AutofillCreditCardDropdownVariations

BUG=

Review-Url: https://codereview.chromium.org/2741043002
Cr-Commit-Position: refs/heads/master@{#456217}

This change adds two bluetooth checks. 1 is to determine if the hardware has bluetooth capabilities. 2 is to determine if bluetooth is on for the device. Both conditions must be met for the PhysicalWebSharing feature to be enabled.

BUG=685856

Review-Url: https://codereview.chromium.org/2737393003
Cr-Commit-Position: refs/heads/master@{#456216}

https://pdfium.googlesource.com/pdfium.git/+log/6791295a4e8c..e472622d33bd

$ git log 6791295a4..e472622d3 --date=short --no-merges --format='%ad %ae %s'
2017-03-10 npm Bound cbox from tricky faces

Created with:
  roll-dep src/third_party/pdfium
BUG=699961

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2741783005
Cr-Commit-Position: refs/heads/master@{#456215}

BUG=632580

Review-Url: https://codereview.chromium.org/2744593005
Cr-Commit-Position: refs/heads/master@{#456214}

This CL removes a mutable reference to ResourceRequest in the argument
of ResourceFetcher::determineRequestContext(),
to reduce mutableResourceRequest() call.

BUG=632580

Review-Url: https://codereview.chromium.org/2742933002
Cr-Commit-Position: refs/heads/master@{#456213}

The argument for OnCheckExtensionsResult should only contain the bad
extensions, but PVer4 code was including all CRXs (blacklisted or not).

BUG=700145

Review-Url: https://codereview.chromium.org/2742913002
Cr-Commit-Position: refs/heads/master@{#456212}

This CL tries to update the last access time for a download item correctly.
The download items have several clients and the access does not go through
a common code path. One option is to look at the file system's last access
time (atime in Unix) and update it from a non-UI thread task. However, it
was found that the last access time is not updated or at best lazily updated
by most of the POSIX systems in case of a file read. So the other approach
is to update the last access time manually whenever the file is opened
through chrome. NTP, download infobar, duplicate download infobar,
download home and download notification are the entry points where
we fire an intent to open the downloaded file. To find the download
item, we need a GUID and the correct profile which was passed correctly
to the appropriate call sites.

BUG=689981

Review-Url: https://codereview.chromium.org/2737723002
Cr-Commit-Position: refs/heads/master@{#456211}

TBR=pdr@chromium.org
BUG=700530

Review-Url: https://codereview.chromium.org/2740843005
Cr-Commit-Position: refs/heads/master@{#456210}

BUG=700057

Review-Url: https://codereview.chromium.org/2743633005
Cr-Commit-Position: refs/heads/master@{#456209}

It is common that FooResource::fetch()-like functions sets
the request context via mutableResourceRequest().
This CL centralizes such mutableResourceRequest() calls into newly
introduced FetchRequest::setRequestContext(), to limit the ways to
modify a ResourceRequest after it is put in a FetchRequest.

BUG=632580

Review-Url: https://codereview.chromium.org/2741753003
Cr-Commit-Position: refs/heads/master@{#456208}

BUG=700499

Review-Url: https://codereview.chromium.org/2742643004
Cr-Commit-Position: refs/heads/master@{#456207}

https://skia.googlesource.com/skia.git/+log/8da9e9407211..e393a629491e

$ git log 8da9e9407..e393a6294 --date=short --no-merges --format='%ad %ae %s'
2017-03-10 reed disable assert until I can understand why it fails in cc_unittests
2017-03-10 jvanverth Add new test cases for Android shadow sample.
2017-03-10 brianosman Revert "Treat cross context images as Ganesh-created resources"
2017-03-10 bungeman Fix SkFILEStream.
2017-03-10 reed Check for bad bounds in picture cullbounds
2017-03-10 brianosman Treat cross context images as Ganesh-created resources
2017-03-10 benjaminwagner Rename GalaxyS7 to include model number.
2017-03-10 fmalita Revert "Revert "Hold sk_sp<GrAtlasTextBlob> refs in GrTextBlobCache instead of raw ptrs""
2017-03-10 fmalita Fix SkTHashTable dangling values
2017-03-10 reed re-guard against negative dimensions on no-draw canvas

Created with:
  roll-dep src/third_party/skia


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
TBR=djsollen@chromium.org

Change-Id: Ic80781b6bb184afa2f6862488cd5574314f6f0e0
Reviewed-on: https://chromium-review.googlesource.com/452673Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#456206}

Review-Url: https://codereview.chromium.org/2744783002
Cr-Commit-Position: refs/heads/master@{#456205}