GitLab

https://chromium.googlesource.com/skia.git/+log/2dcb615c6f48..1e2a702c1959

$ git log 2dcb615c6..1e2a702c1 --date=short --no-merges --format='%ad %ae %s'
2016-07-06 pdr Update dev docs to reference the new skia debugger (skiaserve)

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=rmistry@google.com

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

BUG=625024,622085

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

Add custom UIPresentationController subclass for presenting the picker
selector. The presentation controller sets the frame of the picker
selector to be at the bottom of the screen, and adds a dimming view
behind it.

BUG=622244

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

WebAPKs use WebappDataStorage to store the metadata too.
Some changes in the web app manifest, like themeColor,
orientation etc. don't request re-minting a WebAPK,
but will update the metadata in the SharedPreference
(WebappDataStorage). The metadata will be retrieved
and used for launching a WebAPK.

Registering a WebAPK will be in a following up CL.

BUG=624834

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

This was introduced in https://crrev.com/374212 so find-in-page would
crash less prior to full OOPIF support. It is no longer used and should
be removed.

BUG=none

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

BUG=625936

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

This patch removes the need to add MAYBE lines for nearly every test that goes into find_request_manager_browsertest.cc. It does this by defining a MAYBE() function instead of MAYBE/DISABLED definitions for every test name.

BUG=615291

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

Directories within srcjars are supposed to reflect java package names.
The extra path component was making Android Studio unhappy.

BUG=620034

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

BUG=625909
TBR=fmalita@chromium.org
NOTRY=true

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/59771eda..9c59da50

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_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,yangguo@chromium.org,vogelheim@chromium.org

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

BUG=625584
TBR=mlamouri@chromium.org

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

This is called on any SRTP packet received, and decrypts it in
place. For now the fuzzer uses a hard-coded key and SSRC, but future
modifications could generalise this in a number of ways.

It does read more than one packet, since there could be bugs lurking
in the state maintained by the parser (for example, the ID of each
packet is stored for replay protection).

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

Fixes for UpdatePasswordInfoBarController. SelectorCoordinator is
retained as a property so that it is not immediately dismissed, and
the infobar label is updated in the SelectorCoordinatorDelegate
callback.

BUG=622244

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

Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/9a0de5d..d0d6cf9

TBR=

CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_chromium_archive_rel_ng

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

Cleaning up video-controls-[captions, overlay, track]* tests
in media/ to use testharness.js instead of video-test.js.
This will enable to upstream these tests to web-platform-tests.

BUG=588956

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

Fixes assignment of current versus new password elements in
getPasswordForm to match LocateSpecificPasswords in
password_form_conversion_utils.cc. Previously, the password elements
had been added to the form in reverse order.

BUG=622253

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

BUG=625823
R=haraken@chromium.org
TBR=eroman@chromium.org,yzshen@chromium.org

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

This patch makes |previousPositionOf()| to handle no previous position case,
which is occurred after visible position canonicalization.

It is time to change |DCEHCK()| to return nothing since we have a test case
for it.

BUG=619131
TEST=run_webkit_unit_tests --gtest_filter=VisibleUnitTests.previousPositionOfNoPreviousPosition

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

  In order to roll GN ac799c2f..b9999d69 (r403392:r403866) and pick up
  the following changes:

  511c073b Stop recursion for create_bundle deps when crossing toolchain.
  061d24c1 Fix the script used to roll GN.
  4879cedd Display outputs for "executable" targets in "gn desc".
  3a32f029 GN: Add Windows support to bootstrap.py
  3fed8056 Fix BundleData::GetBundleRootDirOutput() for non-default toolchain.

TBR=dpranke@chromium.org

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

Removed code and the Feature flag related to the
CustomLayout media notification logic since it was replaced with
MediaStyle notification in M52.

BUG=613564

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

In Chromium commit 10749067 catapult was rolled, switching to
default teardowns between pageset repeats, compare [1]. Activating
complex text on Android again after this change in order to see how
measurements are affected by this. If no memory regression shows up in
the memory health measurements for memory pagesets this would indicate
that we may have a memory-leakage over time problem in webview
single-process mode but no issues in the usual tab process lifecycle on
Android. Activating and TBR'ing to collect bot results, potentially
reverting later if needed for further investigation.

[1] https://github.com/catapult-project/catapult/issues/2294

BUG=577306
TBR=eae

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

The changes which this test was added to verify have been
reverted because of issues in MSE playback. So this isn't
testing anything and is not useful.
So removing this test case.

Reverted change: http://crrev.com/1069253004

BUG=588956

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

Changes:
   - BrowsingDataCounter now resides in components/browsing_data/counters/
   - Moved enums and TimePeriod utils to components/browsing_data/browsing_data_utils[.h/.cc]
   - Changes to the counters that still reside in chrome/browser/browsing_data/ are temporary, meant to allow this partial change.
     They will be moved to components in a subsequent CL

TBR=dbeam@chromium.org
BUG=620317

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/3414d38b..59771eda

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_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,yangguo@chromium.org,vogelheim@chromium.org

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

(instead of a string with only a few legal values)

BUG=625161
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

Currently, CompositeEditCommand::moveParagraphs() uses a pair of
VisiblePositions to keep track of original position of the moved
paragraph after it's moved away. However, the VisiblePositions may
be invalidated if their anchor nodes are moved out of document,
causing crashes when the VisiblePositions are used later. It causes
the failure of layout test:

fast/text/first-letter-bad-line-boxes-crash.html

This patch uses RelocatablePosition for the tracking purpose as
a bug fix.

BUG=581038
TEST=fast/text/first-letter-bad-line-boxes-crash.html

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

|RelocatablePosition| is a helper class for keeping track of a |Position| in
a document upon DOM tree changes even if the given |Position|'s original
anchor node is moved out of document. The class is implemented by using a
temporary |Range| object to keep track of the |Position|, and disposing the
|Range| when out of scope.

|RelocatablePosition| will be used in editing code, for example:

https://codereview.chromium.org/2127503002/

BUG=n/a
TEST=webkit_unit_tests --gtest_filter=RelocatablePositionTest.position

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

BUG=625839

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

BUG=None

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

After https://codereview.chromium.org/2092093002, tuples are no longer used
directly in Functional.h.

BUG=597856

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

BUG=623703

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

BUG=624088

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

Adds UpdatePasswordInfoBarController as infobar controller for the
update passwords infobar. UpdatePasswordInfoBarController subclasses
ConfirmInfoBarController, adding an additional link to the label for
choosing an account in the case where multiple accounts are possible for
the password update. Tapping on this link presents a picker view for
selecting the appropriate account.

BUG=622244

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

Blink currently maintains per-page undo stacks, leading to:
- Security risks. A frame can directly manipulate content of another frame
by running document.execCommand('undo'), allowing Javascript to bypass
frame and even origin boundaries.
- Inconsistent behaviors. Without OOPIF, all changes in a page can be undone
by repeatedly invoking keyboard undo (CTRL+Z); With OOPIF, only those changes
in the focused frame and its same-origin frames can be undone.

Redos have analogous defects.

This patch changes UndoStack from per-page to per-frame, so that undos and
redos are consistently resolved by the frame where script is run or which
gets focused.

This CL is a relanding of https://codereview.chromium.org/2110543008 with
the following change:

A new function |UndoStack::clear| is introduced and called in |Editor::clear|.
In this way the leak reported by crbug.com/625736 is not reintroduced.

BUG=349272,549334
TEST=editing/undo/undo-iframe-location-change.html

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

BUG=NONE

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

This allows us to have a more specific OWNERS file than the one in chrome/ or chrome/common/

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

There obviously had to be assignment.

Also I changed return types to be void since they're unused, and
simplified updateMarkerRenderedRect a bit.

Relevant CL: https://codereview.chromium.org/2034363002

R=keishi
BUG=

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

Applications such as Excel put HTML content on the clipboard which
includes STYLE elements. Users expect the styles to remain when
pasting this content.

Chromium used to strip STYLE elements like WebKit. This change leaves
the STYLE elements in place like Firefox and Edge. This means pasted
content could change the formatting of the surrounding page, but
editors could work around this by processing STYLE tags.

BUG=121163

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

This CL introduces a style mixin which can be applied consistently
across pages to show content with the correct padding and width. Using
this mixin fixes an issue where some content was hidden off the left of
the page in small window sizes.

BUG=625057
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

Revert of Add the rest of web platform pointerevent tests (patchset #11 id:200001 of https://codereview.chromium.org/2056333002/ )

Reason for revert:
Pointer event tests fail on linux: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg%29/builds/8274 and Win: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Leak/builds/20854 (possibly others).

Original issue's description:
> Add the rest of web platform pointerevent tests
>
> Add input injection for the rest of web platform
> pointerevent tests.
>
> BUG=612924
>
> Committed: https://crrev.com/23ce92bfe9a1160e552a91d443e788f303f1eb6d
> Cr-Commit-Position: refs/heads/master@{#403812}

TBR=mustaq@chromium.org,dtapuska@chromium.org,rbyers@chromium.org,lanwei@chromium.org,nzolghadr@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=612924

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