GitLab

BUG=650082

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

This CL has no behaivor changes.

BUG=653859, 508728, 627008, 508725
TBR=kojii@chromium.org
NOTRY=true

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

Use a base::Callback to dispatch a SyncLoad result instead of
IPC::Message, so that we can share most of synchronous load code between
Chrome IPC version and Mojo IPC version.

BUG=603396

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

After some discussions the CSS WG agreed that stretch should not only
grow items, but also stretch them to fit its grid area.
That way the "min-width|height: auto" is somehow ignored for grid items.
More info at: https://github.com/w3c/csswg-drafts/issues/283

The good part is that this allows us to remove some ugly code we've
in LayoutBox that was only used by Grid Layout.

The tests have been updated according to the new expected behavior.

For images, we'll be stretching on both axis right nos, so the aspect
ratio won't be preserved. The default behavior might change in those
cases, but that should be implemented in a different patch.

BUG=653433

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

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).

Please review the expectation changes, and LGTM as normal. The recipe roller
will *NOT* CQ the change itself, so you must CQ the change manually.

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug
(or complain)

build:
  https://crrev.com/e10b31caeb97375c3514ae3c9f1a92e28d97b71e analyze: send results to event_mon (phajdan.jr@chromium.org)

R=phajdan.jr@chromium.org
BUG=651536

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Review-Url: https://codereview.chromium.org/2396343002
Cr-Commit-Position: refs/heads/master@{#423838}

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

BUG=563793

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

BUG=555132

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

BUG=webrtc:6484
TBR=phoglund@chromium.org

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

This CL fixes an issue that was preventing foreign fetch to work on
subframes when browser-side-navigation was enabled. The issue was that
there was no way to retrieve the ServiceWorkerContext from the
navigation URLRequest, and so the ServiceWorker specified by the link
header could not be registered.

BUG=440463

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

The fallback isn't needed anymore because DM server has been updated to
send affiliation ids.

BUG=515476
TEST=updated unittest

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

As part of the Content Modularization Project, this CL moves the
implementation of the wake_lock_service.mojom interface from
//content/browser to //device. It also moves that interface itself
out from Blink to //device.

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

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

BUG=647219,651373

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

WebP images are not supported natively on iOS.
This CL adds WebP images decoding to
IOSImageDecoderImpl using webp_decoder.

Most of the work had been done by
markusheintz@chromium.org and then I took over the CL.

BUG=625081

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

BUG=598520

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

BUG=649726

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

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug
(or complain)

build:
  https://crrev.com/57b34f50596d6d4813de992ca854e2284fb5f90f Fix file.copy recipe_module to not fail if files are already equal. (tandrii@chromium.org)
  https://crrev.com/1cd0ad6a13ec82f5670d274d98322388e9b80e3c Revert "Fix file.copy recipe_module to not fail if files are already equal." (tandrii@chromium.org)

TBR=martiniss@chromium.org,phajdan.jr@chromium.org
BUG=636168

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Review-Url: https://codereview.chromium.org/2400863004
Cr-Commit-Position: refs/heads/master@{#423826}

As part of making the Android Blimp APK compatible with the
//blimp/client/public APIs, this first CL moves the session code into
//blimp/client/app. This includes the GN-targets to ensure that they are
easily identifiable as belonging to the app directory.

This moves the APK-target itself, which means that the testing bots
needed to be updated with the new path to the target. In addition, the
lint suppressions needed to be updated with a new path.

The //blimp/client:blimp_unittests_java_deps (moved from //blimp), still
needs to be referred to directly by //blimp/BUILD.gn, because adding it
as a deps to //blimp/client:unit_tests on the Android platform does not
make the Java classes end up in the unit test APK. Other than this, the
rest of the targets have now been moved to //blimp/client and
//blimp/client/app.

Some targets have been renamed since they now reside in the app
directory.

Lastly, since the visibility parts of //blimp/client/core is cleaned up,
a bug was also filed for removing the visibility for internal core
targets for the engine browser tests.

BUG=651964, 653789

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

Removes all WeakNSObjects in already converted implementation files.

BUG=None
TEST=None

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

BUG=647219,651373

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

BUG=647219,648949,651373

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

Port object grouping changes introduced in
https://crrev.com/b7615cfadeb59ac220bd5994d4ec6f99341452f0 to tracing.

Note: Write barriers for incremental tracing will be added in a follow up.

Overview: https://docs.google.com/spreadsheets/d/1RhLiHF9Pnw7Zx8EijuR0LruPkeiVJIXXi0eRkRDFwBc/edit#gid=0&vpid=A3

BUG=chromium:468240
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel
TEST=WebglConformance_conformance_misc_expando_loss,WebglConformance_conformance2_misc_expando_loss_2

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

Overview: https://docs.google.com/spreadsheets/d/1RhLiHF9Pnw7Zx8EijuR0LruPkeiVJIXXi0eRkRDFwBc/edit#gid=0&vpid=A3

BUG=chromium:468240
R=haraken@chromium.org

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

Revert of Delete pre-MD code from OmniboxResultView (patchset #9 id:160001 of https://codereview.chromium.org/2365263006/ )

Reason for revert:
The downstream Chrome on iOS code has never been ported to the new vector icon and still use MD raster icon. This CL breaks Chrome on iOS downstream (due to missing resources and removal of GetIcon() method).

Original issue's description:
> Delete pre-MD code from OmniboxResultView
>
> BUG=648281
>
> Committed: https://crrev.com/255d6d6d2bbc0e8715ad0985d239897f80a4b707
> Cr-Commit-Position: refs/heads/master@{#423690}

TBR=pkasting@chromium.org,blundell@chromium.org,sky@chromium.org,estade@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=648281

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

ASSERT_UNUSED() -> DCHECK()

TBR=haraken@chromium.org

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

SVGAnimateElement is the only user. Move it and make it a free function.

BUG=641437

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

Convenience function to add integers to a WebUIDataSource
without using AddLocalizedStrings with a base::DictionaryValue.

Limits width to 32 bits to prevent integers larger than can
be represented in ES6 (2^53 - 1). (As before, larger numbers
could still be set via AddLocalizedStrings.)

BUG=none
R=tommycli@chromium.org,creis@chromium.org
TEST=content_unittests:WebUIDataSourceTest

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

Helper class for Resource subclasses to prohibit addClient() and removeClient()
calls e.g. in ResourceClient callbacks.

BUG=570205

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

This CL adds a parameter to ContextMenuParams, the inner text of a link on
which a context menu is opened.

BUG=591365

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

This CL imports tests which depend on absolute path resources such as
/common/*.  We resolved the absolute path resource loading issue some months ago.

Some tests are moved in W3CImportExpectations because they have other issues.

| Import wpt@db565f0b6d1e2deadc00e71671d8cda09c9e9736

BUG=498120

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

R=rjkroege@chromium.org
BUG=none

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

Cr-Commit-Position: refs/heads/master@{#423811}

Introduce an applyRuleSetChanges method which will take the old and new
ActiveStyleSheetVector use the existing comparison method and apply the
RuleSet diff to invalidate style for the document.

The normal mode for style rules is to schedule RuleSet invalidations
which will decide what to recalculate based on the invalidation sets.
Universal selectors, the presence of Shadow DOM v0 combinators, or
@font-face rules for the document scope, will cause a subtree recalc
for the TreeScope.

@keyframes rules utilizes the existing functionality for invalidating
style in the TreeScope and the host TreeScope for running and
unresolved animations.

This CL introduces appendActiveStyleSheets which will eventually
replace the combination of the lazy appending of sheets in
StyleResolver and appending pending sheets into the ScopedStyleResolver
through appendCSSStyleSheet.

This CL is split out of https://codereview.chromium.org/1913833002 and
re-worked a bit.

The functionality is not yet in use.

R=meade@chromium.org
BUG=567021

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

Chromium clang plugins depends on clang headers, and the configuration
file assumes it's checked out in a fixed path in the LLVM source tree.
That is inconvenient to build it out of tree.

This CL adjusts the include path setting for external checkout of clang.

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

BUG=328606

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

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug
(or complain)

build:
  https://crrev.com/5ba4397bb3ab875a37501ec8eb0de33d1b4a1514 Wait cloudtail termination in goma module (tikuta@chromium.org)

TBR=martiniss@chromium.org,phajdan.jr@chromium.org
BUG=

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Review-Url: https://codereview.chromium.org/2402493004
Cr-Commit-Position: refs/heads/master@{#423807}

This replaces usage of java DeviceDisplayInfo with DisplayAndroid.
Unfortunately java code generally only pass around the Context instead
of WindowAndroid, so need to officially expose the DisplayAndroid.get
method to the public.

The rest is pretty easy. Only had to add getDIPScale.

BUG=625089

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

Use modified Read and delegate methods from the following CL-
https://codereview.chromium.org/2262653003/

This CL dependents on the following CL as well -
https://codereview.chromium.org/2264973002/

BUG=423484

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

CSSStyleSheets which have a non-matching media attribute may have a
nullptr for RuleSet since it's not needed. Handle that in active style-
sheet diffing. That means adding a sheet with non-matching media should
not cause any style recalculations.

R=meade@chromium.org
BUG=567021

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

No more references to exe:chrome, instead anyone wanting browser
interfaces connects to service:content_browser, which is consistent
with the rest of the universe.

ServiceManager and Catalog have some control interfaces added to
override path resolution for executables and manifests. MashRunner
uses this to direct resolution of "exe:chrome_mash" and
"service:content_browser" accordingly, as well as to resolve
content process manifests to chrome's/mash's overlayed versions
on disk.

Also changes the service_manifest GN template to support overlays.
This makes it easy to reuse the existing overlay metadata with
standalone ServiceManager, as well as to layer multiple overlays
(e.g. content_browser + chrome_content_browser + chrome_mash_content_browser).

Adds a browser manifest overlay specifically for Mash, which is
applied on top of Chrome's own overlay.

BUG=646077
TEST=chrome --mash seems to "work", can set wallpaper, browse cat photos, run task_viewer, etc

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