GitLab

add has_element_in_any_list check in ElementAnimations::UpdateActivation during
PushProperities process. This solves a corner case if dom for animation be
removed before animation starts. See bug for details.

BUG=668086
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/dade4fe3..a72be232

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

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

TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org

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

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

Allow any integer types but always promote the result to unsigned.
This is more consistent with how these operations are normally used.

NOTRY=true

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

Previously the host binary wasn't rebuilt when building
remoting_dev_me2me_host. This CL adds direct dependency between these
targets to avoid this problem.

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

This patch gets rid of |DCHECK()|, which is a wrong assumption, in
|reconcileTextDecorationProperties()| since we have a test case against the
assumption.

BUG=663613
TEST=LayoutTests/editing/execCommand/insert-list-and-strikethrough.html

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

Many subpages show some form of details for a given extension. When the
backing data changes, those changes need to be reflected in the open
subpage. Right now, since the data is just set to the plain JS object,
it's not notified when a change occurs.

Add a subpageItem_ property to extensions page manager so that we can
leverage polymer databinding and link this to the subpages. This way, if
the backing data changes, the open subpage is updated.

Add a test for the same.

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

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

This puts the crash database in the user data directory, rather than in
the global shared one. In order to accomplish this, the variable
expansion from policy needs to be moved to be suitable for use in
chrome_elf. This code handles variable expansions in a registry key that
can be set to override the user data dir (in either HKLM or HKCU).

We do not need to completely remove the usage of DLLs other than
kernel32 in the code despite the code being used in chrome_elf, as in
all cases, it will not execute until after the DllMain() of chrome_elf
has completed, and we load the used functions via GetProcAddress(), not
by import lib. Currently, chrome_elf is signalled from WinMain() of
chrome to start crash reporting. In the near future it will be started
earlier from a background thread spawned in DllMain(). However, that
thread cannot execute until DllMain has completed, so it's then safe to
cause the other DLL loads that the variable expansion requires.

(Regarding the future thread-based spawning, ref:
https://blogs.msdn.microsoft.com/oldnewthing/20070904-00/?p=25283/ which
explains why the creation of the thread with which we don't synchronize
is OK, because DllMain calls are serialized. But we can discuss that
more in https://codereview.chromium.org/2475863004/ too. )

BUG=565446
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

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

The detail view for extensions includes a button to open the extension's
home page (which defaults to the webstore page if an extension doens't
specify one). Hook this up, and add a test.

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

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

BUG=667208

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

Moving milestone to M58.

BUG=605661
TEST=messages logged with EME layout tests

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

Looks like a possible C&P error.  Compile-tested only.

BUG=none
TEST=none
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_nacl_sdk;master.tryserver.chromium.mac:mac_nacl_sdk;master.tryserver.chromium.win:win_nacl_sdk

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

//base's MRUCache allowed specifying key and value types, like
an underlying std::map<>, but the default base::MRUCache explicitly
specialized the comparator as std::less<>. Rather than require the
caller to overload std::less<> or operator<, allow the comparator
to be specified as a templated argument.

BUG=665735

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

Adding getCoalescedEvents API to the idl file
of PointerEventInit and getter method to
PointerEvent idl.
Also add the plumbing and creation in EventHandler
layer and PointerEventManager.

BUG=665937

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

This patch makes |Range::extractContents()| to postpone DOM mutation event
dispatching just before returning value rather than updating C++ variables
which holds |Node*| for every DOM mutation calls, e.g. Node::appendChild(),
Node::removeChild(), etc., to avoid running JavaScript code during in
|extractContents()| for simplicity.

For executing script in |RangeTest|, this patch makes |RangeTest| class to
derived from |EditingTestBase|.

This patch removes
"fast/dom/Range/range-created-in-mutation-event-crash.xhtml" since it causes
script error by calling |Range#getBoundingClientRect()| with |null| value and
coverage of this test is as same as newly added gTest.

This patch is similar to http://crrev.com/199383004 which makes
|Range::deleteContents()| to postpone DOM mutation event.

BUG=642537
TEST=run_webkit_unittets --gtest_filter=extractContentsWithDOMMutationEvent

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

This patch teaches UISourceCodeFrame to display messages from both
UISourceCodes of PersistenceBinding. This is reasonable, since
there might be different "builders" which add messages to either
of the source codes.

This patch also slightly modifies the handling of decorations:
in case of persistence binding, we prefer network uiSourceCode decorations
over the fileSystem ones: it's hard to merge decorations.

This is also an imperative step towards displaying fileSystem file
by default in the editor.

BUG=649837
R=dgozman

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

As they evolved to be quite different and the amount of
common code is minimal, it just make sense to define
which member function is used to render borders and which
is used for backgrounds.

BUG=662504

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

UpdaterState::GetState returns nullptr, if the current platform is
not Windows, and then the test calls at() method on the returned map.

This fixes LTO Linux bot:
https://build.chromium.org/p/chromium.fyi/builders/LTO%20Linux/builds/1560

BUG=615187

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

This patch makes CompositeEditCommand::moveParagraphs abort in the above
mentioned case, because there is no way to move the contents to a destination
inside itself.

There might be a deeper cause of passing such invalid parameter combination
to the function, which is not covered by this patch.

BUG=585048
TEST=webkit_unit_tests --gtest_filter=TypingCommandTest.insertLineBreakWithIllFormedHTML

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

Changes the VR Shell unittests to compile when WebVR is enabled and enables
them on chromium.android builders.

BUG=667964

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

This CL pulls out the content on writing LayoutTests from
layout_tests.md, and does a significant overhaul of it.

BUG=665494

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

Previously, the icon fill color was gray. This change restores it to
white, as the specs indicate.

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

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

This test harness is slowing us down, so we are migrating away from it.

BUG=none

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

Earlier this year the default browser infobar icon was changed to a
stylized blue Chrome icon. This cl, per rpop@, reverts the icon to its
original full-color version.

R=sky@chromium.org
BUG=654340

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

BUG=668321

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

BUG=667644

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

https://pdfium.googlesource.com/pdfium.git/+log/3c0f366daafe..405ac0f09e16

$ git log 3c0f366da..405ac0f09 --date=short --no-merges --format='%ad %ae %s'
2016-11-28 tsepez Use CFX_MaybeOwned<> in fpdf_edit_create.cpp

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/2534063002
Cr-Commit-Position: refs/heads/master@{#434836}

Setting the testing build time ensures that the test passes even if the
system clock is incorrect when running the test.

BUG=668539

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

Only Chrome OS and Windows can choose the language.

BUG=619771
R=stevenjb@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

Implements the "spec" provided as faithfully as makes sense.  This
usually means that values are rounded to the nearest multiple of 8,
but I had to get creative with the definition of the padding above
the "X GB downloaded" TextView because of how Android deals with
top padding for text.

Screenshots:
https://drive.google.com/a/chromium.org/file/d/0B8k2SmEN8xS3QTVELWVhSFlHajQ/view?usp=sharing
https://drive.google.com/a/chromium.org/file/d/0B8k2SmEN8xS3ZDczcV9aZ0ctLWs/view?usp=sharing

BUG=658246

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

This CL adds a separator above the sticky header rows when those rows
are not at the top of the list. The visible separator line is drawn by
this separator and is no longer a part of the sub-section header row.
The sticky row decoration is adjusted such that a separator is painted
only when one header is pushing another since in all other cases the
explicitly added separator is painting the line.
Since VPN page is not using sticky headers yet some special treatment
is added there to adjust the height of the header row when it is the
first item in the list.

BUG=668545
TEST=Manual visual inspection

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

Before this CL, OnMemoryStateChange() only handles "purge" part
of purge+suspend mechanism. Handle "suspend" part as well.

BUG=617492

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

The Hotword/OK Google section in the existing UI is... fragile.
This is an attempt to simplify and implement the UI without breaking
any existing functionality.
It would benefit from a re-implementation, ideally ising the
existing hotwordingPrivate API (which would may need to be expanded).

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

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

Multisampled render to texture appears to be broken on Android 7.1 and
Adreno 5xx, similar to issues reported in Android < 7.0. This is fixed
in 7.1.1.

We should confirm that this is working in 7.0 if possible. The device
where this issue was reported (Pixel XL / Pixel) didn't ship with 7.0.

This issue appears to result in multisampled rendering failing to
produce output in cases when rendering to a texture that has already
been used in a previous render pass.

BUG=663811
CQ_INCLUDE_TRYBOTS=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/2514283002
Cr-Commit-Position: refs/heads/master@{#434829}

Just a refactor. No change in behavior, no new tests.

Pull up updateRequiredPreviousFrameAfterFirstDecode,
resumePartialDecodingAfterClearFrameBufferCache, which are shared by
GIFImagerDecoderTest and WEBPImageDecoderTest.

Pull up testAlphaBlending from WEBPImageDecoderTest, so that it can be
reused in APNG tests.

Use ImageDecoderTestHelpers::testByteByByteDecode for GIF's
parseAndDecodeByteByByte test. This tests for the same, and in addition
checks if the baseline hashes are equivalent to the incremental hashes.

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

Couple minor visual tweaks to the Add Word row; see screenshots at
https://crbug.com/630982#17.

BUG=630982
R=stevenjb@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

BUG=667779,667797

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

No change in functionality. Expectation lines adjusted to make
ownership clear.

TBR=chrishtr@chromium.org
BUG=

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

AMD drivers do not correctly handle the pattern of DX calls generated
by ANGLE for glTexStorage2DExt. We've worked around the known
problematic case in crrev.com/2507963003, so this change removes the
GPU raster blacklist.

It's possible that this issue is still hittable from Skia, and likely
from WebGL2, so it makes sense to try to work around this in ANGLE or
to blacklist glTexStorage2DExt.

Unfortunately, the ANGLE code in this area is quite complex, and a
workaround is a ways out. Additionally, there's no way to disable
glTexStorage2DExt without losing all of WebGL2, which seems non-ideal.

BUG=660897
CQ_INCLUDE_TRYBOTS=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/2521803002
Cr-Commit-Position: refs/heads/master@{#434824}

This adds the SHA-256 of the RSA key that we use to sign CRX packages on
Chrome.

BUG=630420

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