GitLab

https://skia.googlesource.com/skia.git/+log/8b4b56ac2927..b048e81c5c27

$ git log 8b4b56ac2..b048e81c5 --date=short --no-merges --format='%ad %ae %s'
2016-12-05 borenet Roll recipe DEPS

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=herb@google.com

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

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

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

Multiple concurrent fetch processes ensure that the UI will always get
a correct response for a |Fetch| request.
In order to bind fetcher and callback to the request, a new |Request|
class provides another layer of abstraction.

(No tests were deleted. The test "ShouldCancelOngoingFetch" is not part of the use case anymore and was replaced with "ShouldProcessConcurrentFetches")

BUG=659931

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

This patch adds a histogram which tracks a how many style sheets reach
certain rule usage milestones (i.e. > 10% rules used).

This is useful for determining how worthwhile lazy parsing is in the wild.

BUG=642722

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

This change moves logic related to IPC requests regarding a single stream into its own class. This prepares for adding a mojo alternative to ARH. The mojo implementation will have a separate interface for an audio stream, which makes it very reasonable to have a class responsible for handling requests to a stream. This change also slims down ARH, so that it's easier to replace.

Reference for mojofication work: https://docs.google.com/document/d/1PjV_EutyJANmsEjhH9mTNZWSslTPvAit7Cy2RO3cbmk/edit, in particular the diagram https://docs.google.com/drawings/d/1xg6z2FwLdTe5eG-Nvek9q-IfWzMI01XxlbVH3y0mzAE/edit.

BUG=656923
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_msan_rel_ng,linux_chromium_chromeos_asan_rel_ng,linux_chromium_chromeos_msan_rel_ng,linux_chromium_tsan_rel_ng,linux_chromium_ubsan_rel_ng;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel,mac_chromium_asan_rel_ng;master.tryserver.chromium.win:win_optional_gpu_tests_rel,win_chromium_syzyasan_rel

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

Notable changes: none

BUG=665024

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

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

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

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

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

This adds an application class, an instrument class and a skeleton
bridging class which can later be implemented to communicate with the
service worker class in C++.

The app factory class has been extended to create instances of the new
web based payment apps in addition to the existing autofill payment app.

BUG=669876

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/cae2c86e..f295aa2a

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

BUG=670562
R=tzik@chromium.org

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

This CL removes the old image fetcher as it has been moved to ImageDataFetcher.

BUG=667747

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

This is part of an experimental feature Embedding-CSP.

Here we add support for `none` source lists. Note that
normalized returned CSP might not explicitly declare `none`, but
with contradictory sources can allow effectively `none`.

For example if the secure origin is `http://google.com`:
Content-Security-Policy: script-src 'self'
Content-Security-Policy: script-src https://example.test/

then it should be subsumed by the Embedding-CSP that is :
Content-Security-Policy: script-src 'none'

BUG=647588

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

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

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

Allow the following to timeout or pass.

http/tests/streams/writable-streams/write.https.html
imported/wpt/encoding/textdecoder-labels.html
virtual/mojo-loading/http/tests/streams/writable-streams/write.https.html

TBR=joelo@chromium.org, ricea@chromium.org
NOTRY=True
BUG=671158

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

This is needed for Chromium builds in debian/arm64
and matches how arm, x86 and x86_64 also have
both clang and gcc toolchains available.

R=brettw@chromium.org, dpranke@chromium.org, scottmg@chromium.org

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

This CL allows MediaSession in iframes to be routed, as per spec change:
https://github.com/WICG/mediasession/pull/149

To achieve this goal, class MediaSessionServiceRouter is added for selecting
which MediaSession object to route.

The current MediaSessionService routing strategy is:

* If the top-level frame uses MediaSession API, always select the
  top-level session.
* If the top-level frame has no MediaSession, select one of an
  audio-producing frame, and route its session (or null if the frame
  does not use MediaSession API).

CL explanation:
https://docs.google.com/a/google.com/document/d/1Ht6DxjOcfBctfRT3_wOkwGoNUaJY-Q8K18MV3xdAh_8/edit?usp=sharing

BUG=670319

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

The dummy Frame on Workers has EmptyFrameScheduler, and it returns a
WebTaskRunner for the current thread. However, since all Frame should
belong to the main thread, the resulting WebTaskRunner should run on
the main thread even when the task runner is requested on a non-main
thread.
This CL ensures EmptyFrameScheduler to use the main thread task runner.

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

From Android M app restrictions may contain bundles and arrays of
bundles. Support this in Chrome. Convert them to JSON for transfer
to the native side.

BUG=525441

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

Fixes a wrapper tracing issue where ExtensionTracker and WebGLAttachment were
not handled properly. Has no affect on regular Oilpan garbage collection.

With wrapper tracing enabled this could've resulting in wrappers for typed
extensions and attachments being prematurely collected.

The issue was flushed out when we were able to generate compile-time errors
instead of having a catch-all dispatcher at runtime in
http://crrev.com/2533383003.

BUG=chromium:468240
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

Committed: https://crrev.com/fb0beca59e6cc67a6f5b599476c8a3b27ce0418b
Review-Url: https://codereview.chromium.org/2539113002
Cr-Original-Commit-Position: refs/heads/master@{#435262}
Cr-Commit-Position: refs/heads/master@{#436263}

Firefox abandoned usage of the moz_bookmarks_roots table since v. 30 and
removed the table in v. 31 in favor of storing relevant info in the
'guid' column of the moz_bookmarks table.

BUG=638977

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

TBR=rdevlin.cronin@chromium.org
NOTRY=True
BUG=671144

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

Using the promise-based getStats to collect stats, writes stats after
60+10* seconds of audio and video calling. These will be picked up by
the Chrome Performance Dashboard[1]. E.g. from other browser test: [2].
*(After 60s of ramp-up, performs measurments during a 10s window, to
avoid unstable stats due to variations in ramp-up time.)

This is similar to the WebRtcPerfBrowserTest - renamed
WebRtcInternalsBrowserTest to avoid confusion - which instead uses
chrome://webrtc-internals relying on the old callback-based version of
getStats. Available stats are different.

This performance test only picks up:
- browser_tests / audio_[codec] / send_rate
- browser_tests / audio_[codec] / receive_rate
- browser_tests / video_[codec] / send_rate
- browser_tests / video_[codec] / receive_rate
Based on "RTC[In/Out]boundRTPStreamStats.bytes_[sent/received]" values
[3][4].
For audio codecs: opus, ISAC, G722, PCMU, PCMA.
And video codecs: VP8, VP9, H264.

More stats can be picked up in follow-up CLs, but the new getStats API
has a limited number of stats available.

[1] https://chromeperf.appspot.com/
[2] https://chromeperf.appspot.com/report?sid=4a337ff35047d3a12a0b6d05fa1bf95e001c824cd1821be95dc7799134ae9b67
[3] https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-bytessent
[4] https://w3c.github.io/webrtc-stats/#dom-rtcinboundrtpstreamstats-bytesreceived

BUG=670306, 627816

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

BUG=537054, 666061
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/2548273002
Cr-Commit-Position: refs/heads/master@{#436259}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/11c28061..cae2c86e

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

This patch is intended to confirm if the previous change can fix the
issue that fires these CHECKs. Once this patch can survive for some
days, I'd change them to DCHECKs. Otherwise, I'd revert this patch, and
find another potential issues.

Please feel free to revert this patch when you notice some crashes
that are caused by this patch.

BUG=670638

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

Add Arm64 linux support be able to build GN binary for
native arm64 builds.

R=dpranke@chromium.org, brettw@chromium.org

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

TextIterator's behavior with first-letter is broken:
1. If its starts in a text node with first-letter and the starting
offset is non-zero, wrong text is passed to its text state.
2. When the text state is handling the remaining text of first-letter,
it doesn't consider the length of first-letter, and hence, reports
wrong offsets of the current text.

To fix 2, this patch makes the text state remember the length of
first-letter, and use it to adjust the output of
start/endOffsetInCurrentContainer.

To fix 1, given that the current behavior is correct when we start in
a text node at offset 0 (even with first-letter), this patch performs
a reduction that:
- start iterating with offset 0 instead of the given start offset
- have extra calls of |advance()| during initialization so that we have
moved to the given start position when initialization ends
- adjust text run start and end offsets when emitting text of the starting
text node

This patch partially corrects the behavior in two layout tests:
- editing/selection/extend-by-word-002.html
- editing/text-iterator/first-letter-word-boundary.html
The tests are still failing for other reasons, see crbug.com/671104

This patch is not an ultimate fix of TextIterator's behavior with
first-letter, but more like a first-aid hack built upon the current design.
In the long term, we should rewrite TextIterator.

BUG=647080

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

Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/42ad2d4..6926a7d

$ git log 42ad2d4..6926a7d --date=short --no-merges --format=%ad %ae %s
2016-12-02 deadbeef@webrtc.org Revert of Disable P2PTestConductor.LocalP2PTestDtlsBundleInIceRestart under msan (patchset #1 id:1 of https://codereview.webrtc.org/2546913003/ )
2016-12-02 deadbeef@webrtc.org Allow locally rendered video to be downscaled in end-to-end tests.
2016-12-02 zhihuang@webrtc.org Modify the parameter type of PeerConnectionObserver callback OnAddTrack.
2016-12-02 deadbeef@webrtc.org Revert of Use different restrictions of acked bitrate lag depending on operating point. (patchset #3 id:40001 of https://codereview.webrtc.org/2542083003/ )
2016-12-02 sergeyu@chromium.org Fix exponential probing in ProbeController.
2016-12-02 asapersson@webrtc.org Turn off error resilience for VP9 if no spatial or temporal layers are configured and NACK is enabled.
2016-12-02 stefan@webrtc.org Use different restrictions of acked bitrate lag depending on operating point.
2016-12-02 sprang@webrtc.org Wire up rtcp xr target bitrate on receive side.
2016-12-02 charujain@webrtc.org Added tool for reference less video analysis (go/refless-video-analysis)
2016-12-02 nisse@webrtc.org New gn target video_frame_api.
2016-12-02 kjellander@webrtc.org Remove xdisplaycheck
2016-12-02 howtofly@gmail.com fix coding and documentary ambiguity in AimdRateControl::TimeToReduceFurther.
2016-12-02 henrik.lundin@webrtc.org Disable P2PTestConductor.LocalP2PTestDtlsBundleInIceRestart under msan
2016-12-02 magjed@webrtc.org VP8DecoderImpl: Fix uninitialized memory crash
2016-12-02 ossu@webrtc.org Deprecated SetAudioPacketSize from RTPSender and removed calls to it.
2016-12-02 henrik.lundin@webrtc.org Remove API-related #defines from voice_engine_configurations.h
2016-12-02 kthelgason@webrtc.org Sanity check parsed QP values from H264 bitstream
2016-12-01 deadbeef@webrtc.org In end-to-end PeerConnection tests, allow video to be downscaled.
2016-12-01 deadbeef@webrtc.org Revert of Disabled flaky P2PTestConductor tests on ASAN and MSAN. (patchset #1 id:1 of https://codereview.webrtc.org/2539103002/ )
2016-12-01 deadbeef@webrtc.org Relaxing timeouts for TestMediaMonitor.
2016-12-01 deadbeef@webrtc.org Relaxing DCHECK for packets sent before SRTP is enabled.
2016-12-01 henrik.lundin@webrtc.org Add linearly spaced counting histograms
2016-12-01 danilchap@webrtc.org Cleanup RtpHeaderExtensionMap removing use of two legacy functions
2016-12-01 terelius@webrtc.org Remove bitrate cap for AdaptiveVideoSource and increase other caps to 25 Mbps.
2016-12-01 sprang@webrtc.org Wire up BitrateAllocation to be sent as RTCP TargetBitrate

TBR=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
BUG=

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

It is deprecated in webrtc, to avoid dealing with half-initialized
objects.

BUG=None.

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

Re-land of https://codereview.chromium.org/2534633002/

In order to have a perf test looking at stats of interest we need to be
able to get the results of a JavaScript getStats call. These can be
returned as JSON-stringified JavaScript dictionaries.

In this CL:
- [g|G]etStatsReportDictionary added to webrtc_browsertest_base.cc and
  peerconnection_getstats.js, which produce/read a JSON-stringified
  version of the stats.
- RTCStatsReportDictionary and RTCStatsDictionary, helper classes for
  reading stats from the base::Dictionary representation of the stats.
- Unittests for the helper classes.

In a follow-up CL these methods/classes will be used to obtain the
stats in the to-be-added performance test. This will yield pretty
graphs.

BUG=670306, 627816

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

Revert of Use the modal view when signing in from chrome.identity extension API. (patchset #2 id:10001 of https://codereview.chromium.org/2462603002/ )

Reason for revert:
This CL as it is responsible for crash
https://bugs.chromium.org/p/chromium/issues/detail?id=667750

Original issue's description:
> Use the modal view when signing in from chrome.identity extension API.
>
> BUG=652791
>
> Committed: https://crrev.com/8122f2f2f0ba7bd36c264f03dd6201232335bdcb
> Cr-Commit-Position: refs/heads/master@{#429556}

TBR=anthonyvd@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=652791, 667750

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

Re-ran generate_buildbot_json.py. The JSON diffs were applied
incorrectly by the CQ.

BUG=369849, 624436
TBR=zmo@chromium.org
NOTRY=true

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

Although there are metrics for the budget and SES at the time that budget
is consumed, there isn't currently any tracking for which events in the
budget system come via the Budget API interface.

This adds two new metrics, to track queries and reserve requests. It also
adds some basic testing to ensure the metrics are being recorded.

BUG=617971

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

In preparation for async stylesheet update, schedule a layout tree
update when marking tree scopes dirty for active style sheets. This is
necessary to trigger a beginFrame which will in turn call
updateActiveStyle as part of the lifecycle update.

R=meade@chromium.org
BUG=567021

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

BUG=537054, 666061
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/2547393002
Cr-Commit-Position: refs/heads/master@{#436247}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/cd7151a2..11c28061

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

R=hayato@chromium.org
BUG=none

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

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

Removes unnecessary Document::wrap and associateWithWrapper.
The special code in these functions were made in order to keep
WindowProxy::m_document updated and consistent with toV8(document).
But we no longer rely on the hack, and we can remove the dead code.

WindowProxy::m_document is used to support named properties on the
document, and only used in WindowProxy::namedItem{Added,Removed}.
These functions are only called from ScriptController::namedItem
{Added,Removed} and ScriptController already guarantees that the
WindowProxy is initialized at once.  So, there is no need for
Document::wrap to call WindowProxy::updateDocumentProperty.

Plus, this CL removes WindowProxy::m_document.  Given that we knew
it's the main world, we should be able to retrieve the wrapper
object of the document in almost the same speed as before.  The
new code to retrieve the wrapper object should be almost equivalent
to
    ScriptWrappable::mainWorldWrapper(isolate)
and it's almost the same as
    m_document.newLocal(isolate)

The first attempt was: http://crrev.com/2525313004

BUG=

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