GitLab

Break the dependency on LayoutObject for NinePieceImage painting and for
border painting by updating NinePieceImagePainter to instead take a Node
and a ImageResourceObserver reference. Also moves border painting to the
BoxPainterBase class as border painting can now be shared with LayoutNG.

R=pdr@chromium.org
BUG=714962
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

Crash reports for https://crbug.com/723414 show a crash in a CHECK()
of profile type being used to create a new browser window via
Browser::Browser(), specifically:

  CHECK(!profile_->IsGuestSession() || profile_->IsOffTheRecord())
      << "Only off the record browser may be opened in guest mode";

This cl forces SessionStartupPref::GetStartupPref() to return default
startup prefs for guest profiles.

R=sky@chromium.org
BUG=723414

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

The refactor https://chromium-review.googlesource.com/536475 lost a pair of
parentheses, so the division by epsilon_seconds was just dividing one of the
matrix elements instead of the difference. This broke angular velocity
calculation.

BUG=735155

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

BrowserThread::FILE is deprecated in favor of the post_task API.

BUG=689520

Change-Id: Ib93ffbf44c692f7effdcc717c20ddca6ceed0e74
Reviewed-on: https://chromium-review.googlesource.com/540668Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480945}

BUG=733722
TEST=manually with flag --force-device-scale-factor=2

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

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

Modifies the ARC account provisioning for Active Directory users.
Does not show a ToS page since for AD users both arc-enabled and
metrics-enabled policies are always managed and the backup-and-
restore and location-services prefs are unused as DM server creates
LaForge accounts for AD users.
Instead, shows a page informing the user that they have to
authenticate with Active Directory. This is necessary to prove the
user's identity to DM server for creating the LaForge account. The
prove of identity works through a SAML flow.
ArcActiveDirectoryEnrollmentTokenFetcher pops up a browser window
connecting to AD Federation Services. Without the shown page, it
would be weird to pop up a browser window that might ask for
credentials.
The backup-and-restore and location-services prefs are left untouched
at their defaults, which is off.

BUG=chromium:728188
TEST=out/Release/unit_tests --gtest_filter=Arc*

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I9f6a63038705e71d29a92557a2b62325eae23d0b
Reviewed-on: https://chromium-review.googlesource.com/521502Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480942}

Revert of Change memory dumps to not use periodic dumps by default. (patchset #3 id:40001 of https://codereview.chromium.org/2912483002/ )

Reason for revert:
This breaks periodic dumping on Android. Reverting.

Original issue's description:
> Change memory dumps to not use periodic dumps by default.
>
> The only consumer that requires periodic dumps [and doesn't specify an explicit
> dump config] is Chrome tracing, so explicitly specify a periodic dump config
> there. Remove by default the periodic dump config.
>
> BUG=726393
>
> Review-Url: https://codereview.chromium.org/2912483002
> Cr-Commit-Position: refs/heads/master@{#475608}
> Committed: https://chromium.googlesource.com/chromium/src/+/0529413d84c06f3720bf4a56b28bb2c7358cefd1

TBR=primiano@chromium.org,ssid@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=726393

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

Chromoting host no longer needs API Key, so the key can be removed.

Change-Id: I0960660ce2ddd5f4352ab691468d7c3881530d8d
Reviewed-on: https://chromium-review.googlesource.com/540035Reviewed-by: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480940}

We now have enabled external/wpt/2dcontext in our layout tests, and that
covers everything that is in the LayoutTests/canvas/philip dir.

This CL will be the first step to remove redundant canvas layout tests.
Basically I removed everything under canvas/philip/. There are 7 tests
under LayoutTests/canvas dir, and I moved them to fast/canvas/. With that,
some of the expectation files are updated. To sum up, this CL removes
more than 800 layout tests without loss of test coverage, and it should
not cause behavior change at all.

Bug: 725651
Change-Id: I3d187a2f283d8ad5615eea3ae18fe77a5b3da28e
Reviewed-on: https://chromium-review.googlesource.com/538597
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Reviewed-by: Ojan Vafai <ojan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480939}

R=dpapad@chromium.org
BUG=567770
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

This reverts commit 1d629632.

Reason for revert: Failures on Win7 Debug (NVIDIA). See crbug.com/735175.

Original change's description:
> gpu: Add message filter destructor stack traces to crash keys.
> 
> base::debug::Alias values don't show up in minidumps. Using crash keys
> is recommended for use-after-free bugs in the following doc:
> http://dev.chromium.org/developers/debugging-with-crash-keys
> 
> R=​jbauman,rsesek,sandersd
> BUG=729483
> 
> Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> Change-Id: I8fd129daf66dc9235307a28fe5cd7a6c23b85a94
> Reviewed-on: https://chromium-review.googlesource.com/538056
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Reviewed-by: John Bauman <jbauman@chromium.org>
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#480879}

TBR=jbauman@chromium.org,sandersd@chromium.org,sunnyps@chromium.org,rsesek@chromium.org

Change-Id: Ic7a35e90b386234652835cd463911f6ad9b0d332
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 729483
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/541756Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480937}

Bug: 734102
Change-Id: I626132775aba216400a0c0b536ec4a65797b7430
Reviewed-on: https://chromium-review.googlesource.com/538237
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Shivani Sharma <shivanisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480936}

BUG=734442

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

//device/generic_sensors already has all the sensors that can be used
to implement the DeviceOrientation event:
https://w3c.github.io/deviceorientation/spec-source-orientation.html

Currently, //content/renderer/device_sensors uses sensors from
//device/sensors as its backend, and this is one of the CLs that refactor
//content/renderer/device_sensors to use sensors from
//device/generic_sensor as the backend and removes //device/sensors.

This CL refactors DeviceMotionEvent to use sensors from //device/generic_sensor.

The issue page contains the design doc link for this change.

BUG=721427

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

The most important thing that this gives us is the symbolizer data
dependencies in //base (for producing symbolized stack traces on the
swarming bots) but it also allows us to clean up the gn files in a
few places.

R=thakis@chromium.org
BUG=732652

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

Adds localization for the custom schedule slider legend
marker lebels, as well as the time bubbles.

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

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

TBR=rockot@chromium.org

BUG=NONE

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

This CL removes some js includes that don't appear to be in use any longer.

BUG=677338

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

OnSurfaceCreated is not called for pre-existing surfaces. This leads
to the DisplayScheduler ignoring expected surface damage. This patch
removes the use of OnSurfaceCreated and initializes tracking state in
OnSurfaceDamageExpected instead.

Bug: 734942, 697086
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I737293e3b72202aa5fc7fdb4dd6aab4937aabea7
Reviewed-on: https://chromium-review.googlesource.com/541278
Commit-Queue: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480929}

Running the static_initializers tool on the canary build of
chrome_child.dll showed a few dozen static initializers. It was run like
this:

    > tools\win\static_initializers\static_initializers.exe chrome_child.dll | find "obj/" | find "initializer"

Many of these are trivially avoidable by tagging the objects in question
as constexpr. This saves some startup cost, some code size, and it
avoids creating so many private pages in the data segment. Testing with
a non-official 32-bit release build shows that this change avoids eight
static initializers. Once we switch to VC++ 2017 we will be able to use
constexpr in more places.

The static keyword was removed in a few places because it is redundant
to const/constexpr.

The effect on non-VC++ builds is unknown. It should be strictly
neutral or an improvement.

BUG=341941
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

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

After https://codereview.chromium.org/2872343003/ dispatching to input method
has moved to WindowEventDispatcher, which should also work for Cast.

BUG=NONE

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

BUG=

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

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

TBR=charliea@chromium.org

Bug: 735107,713222
Change-Id: I514c99a7cf93c4f90ba00f6ee9afd7044fb805ff
Reviewed-on: https://chromium-review.googlesource.com/541617Reviewed-by: rnephew <rnephew@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: rnephew <rnephew@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480924}

This field indicates whether a tab is in a visible window. It will
be used to allow tabs in non-visible windows to be discarded.

This CL does not change any observable behavior.

Bug: 731145
Change-Id: I00206e5213da1cfbefd056fe4f66ac3571334847
Reviewed-on: https://chromium-review.googlesource.com/539855Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Commit-Queue: Francois Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480923}

https://codereview.chromium.org/2925073002/ moved this from blink to
base. This doesn't seem to be exposed from musl so filed bugs and
stubbed (as it doesn't compile right now.)

Bug: 706592, 735087
Change-Id: I106eb6875d4ba7b283d831ba33aded5f850c9e1b
Reviewed-on: https://chromium-review.googlesource.com/541655Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480922}

This test is flaky on all platforms:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=css3%2Fblending%2Fbackground-blend-mode-gif-color-2.html&testType=webkit_tests

TBR=schenney@chromium.org

Bug: 734422
Change-Id: Id3a880f6514e7f6b31f43f91d13bf84e21f6f776
Reviewed-on: https://chromium-review.googlesource.com/540787Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480921}

In some situations, table percentage widths exceed 100%, causing
division by zero. The previous code would divide by an arbitrarily
small number to avoid division by zero and get an arbitrary high
value. Since FF/Edge always set to a max width (which is still
unspecified), we now also set to a max width (kMaxTableWidth). 

Bug: 
Change-Id: I2baae89addc89417aa7999c84e17ef5dfbc588ab
Reviewed-on: https://chromium-review.googlesource.com/540261Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Joy Yu <joysyu@google.com>
Cr-Commit-Position: refs/heads/master@{#480920}

This test is flaky on all platforms:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&showExpectations=true&tests=fast%2Fevents%2Fwheel%2Fmouse-wheel-scroll-latching.html

TBR=sahel@chromium.org

Bug: 735130
Change-Id: I1268bfd45c2df6623cfc334de8db0cfb4e218780
Reviewed-on: https://chromium-review.googlesource.com/541715Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480919}

Xcode 8.3.2 requires macOS 10.12+. This version of Xcode 8.3.2 has both the
10.10 and 10.12 SDKs, and builds will continue to use the 10.10 SDK.

BUG=624049

Review-Url: https://codereview.chromium.org/2941293003
Cr-Original-Commit-Position: refs/heads/master@{#480685}
Committed: https://chromium.googlesource.com/chromium/src/+/abd9ba0ebfca0ce7a37c14593d55ebee56c4a55c
Review-Url: https://codereview.chromium.org/2941293003
Cr-Commit-Position: refs/heads/master@{#480918}

Within the Indexed DB back end code, use BindOnce when posting tasks
and setting mojo pipe connection error handlers, and make transaction
operations OnceCallbacks since they never execute twice.

(The storage::QuotaClient API still requires the generic base::Bind
for now even though the callbacks are logically Once.)

BUG=714018

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

UMA data shows that users disambiguate to the touch adjustment preferred
node twice as often as the next best candidate.  This shows the
disambiguation feature is overtriggering -- ideally, the probability
would be equal.

There is already logic to throw out candidates if their overlap area is
strongly outweighed by the best candidate.  This uses an arbitrary ratio
of 50%.  Increasing it to 75% doesn't visibly undertrigger when I expect
it to on desktop NYTimes sidebars on my Nexus 6P, so try that threshold
to improve the stats.

BUG=704323

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

BUG=701032

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/e644f98aab3b..821867d51814

$ git log e644f98aa..821867d51 --date=short --no-merges --format='%ad %ae %s'
2017-06-20 sullivan Update perf dashboard documentation links

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=sullivan@chromium.org

Change-Id: I9b2877fedccf0b4429e55f18716ff05095df6513
Reviewed-on: https://chromium-review.googlesource.com/541600
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480914}

Update MaxColspan value from 8190 to 1000 for below.
a) colspan attribute of td and th elements.
b) span attribute of colgroup and col elements.

Spec change:
https://github.com/whatwg/html/pull/1993
https://github.com/whatwg/html/pull/2734

Spec:
https://html.spec.whatwg.org/#dom-tdth-colspan
https://html.spec.whatwg.org/#dom-col-span
https://html.spec.whatwg.org/#dom-colgroup-span

BUG=715559

Change-Id: I90807a5c30cd4b0985de5d4cde6ebaa04cfa7fea
Reviewed-on: https://chromium-review.googlesource.com/539435Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Shanmuga Pandi <shanmuga.m@samsung.com>
Cr-Commit-Position: refs/heads/master@{#480913}

Note not all functionality of the tab helper is tested, only added one.
Filed a bug (734759, FixIt) for tests for the rest of it.

Bug: 701939
Change-Id: I151b16894d454ffca889b2580135fa60745b8294
Reviewed-on: https://chromium-review.googlesource.com/540496
Commit-Queue: Dmitry Titov <dimich@chromium.org>
Reviewed-by: Jian Li <jianli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480912}

Wire up UserActivityForwarder in the browser process so that code that
uses UserActivityDetector won't crash and will get correct activity
notifications.

Bug: 716244
Test: manual, run chrome --mash on enterprise enrolled device, no crash
Change-Id: I3d6d5aeabde2880e053738847ca08c3813efab86
Reviewed-on: https://chromium-review.googlesource.com/540282Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480911}

Bug: 712963
Change-Id: Id694978ae94a019f91a27a37b6b0f552169df728
Reviewed-on: https://chromium-review.googlesource.com/538972
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#480910}

https://skia.googlesource.com/skia.git/+log/012bdf8cb526..ffa8484eb061

$ git log 012bdf8cb..ffa8484eb --date=short --no-merges --format='%ad %ae %s'
2017-06-20 reed Revert "Revert "remove unused api on xfermodeimagefilter""
2017-06-20 reed Revert "Revert "remove unused api""

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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=halcanary@chromium.org

Change-Id: I5332c1d99e99b677a7657eb2ac03c89b56152f70
Reviewed-on: https://chromium-review.googlesource.com/541657Reviewed-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@{#480909}