- 24 May, 2019 40 commits
-
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/316f3ac13b51..f3db34d06074 git log 316f3ac13b51..f3db34d06074 --date=short --no-merges --format='%ad %ae %s' 2019-05-24 srte@webrtc.org Revert "Cleanup of video packet overhead calculation." 2019-05-24 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 8b25075e..8ae1a64b (662811:662926) Created with: gclient setdep -r src/third_party/webrtc@f3db34d06074 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie941b7032f76d31ae925edffedbddedc6b8fd9dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628345Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#663020}
-
Simon Zünd authored
The web-test "non-fast-scrollable-region-nested.html" layout test passes a DOMRectList directly to Array#sort. This CL spreads the DOMRectList into an actual JSArray, making it sortable. R=adamk@chromium.org Bug: v8:8714 Change-Id: Iaa380a7522a3e65f922e42720f278c0236305c53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627386 Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#663019}
-
Maksim Moskvitin authored
Once client received default NigoriSpecifics during initial sync it should fill NigoriSpecifics with keystore Nigori and commit changes to the server. This CL adds integration test for this case. Bug: 922900 Change-Id: I6bd3443fb699aeeb3609183377204a75b76fa6cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609823 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#663018}
-
Pâris MEULEMAN authored
This CL extends the java |SigninManagerDelegate| interface and its android implementation |ChromeSigninManagerDelegate| with |isGooglePlayServicesMissing| and |canUseGooglePlayServices|, removing |ExternalAuthUtils| and |UserRecoverableErrorHandler| dependencies from |SigninManager|. Bug: 963400 Change-Id: I5faadf64e9e1565ca3eb458ae02ed8085e1f17bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613085Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org> Cr-Commit-Position: refs/heads/master@{#663017}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/583fc3036847..ff5c0bfd8dc2 Created with: gclient setdep -r src-internal@ff5c0bfd8dc2 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=yukishiino@google.com,lgrey@google.com,masonfreed@google.com,rsorokin@google.com Change-Id: I2e82ed413c29ad2499ff0eed19c97179ac78e170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628346Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#663016}
-
Morten Stenshorne authored
fit-content in the block direction has little or no effect after the fix for bug 902863, but we had settings UI CSS that depended on them. The :host in settings_subpage.html used to be able to get the right height propagated all the way from #main in settings_ui.html, but that's no longer possible (since we cannot give #main a definite height anymore). Therefore, use the viewport height instead, and subtract the space taken up by the top toolbar. Now chrome://settings and subpages, such as chrome://settings/content , render as expected again. Bug: 965858, 965859 Change-Id: I966790ad21e018abdc8f3af91dc102594de340db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624905Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#663015}
-
Maksim Moskvitin authored
After receiving the Nigori with explicit passphrase type bridge requests passphrase via OnPassphraseRequired() observer's method. Calling OnPassphraseRequired() should make UI ask for passphrase and calling SetDecryptionPassprase() once it is provided. UI part is responsible for verifying passphrase by using pending keys exposed by OnPassphraseRequired(). This CL doesn't contain logic for SCRYPT key derivation method and triggering Nigori rewrite in case we have additional encryption keys locally. Bug: 922900 Change-Id: I59d9fb48773232c68631e8c1ce5cd7863b638fa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1621911 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Kenichi Ishibashi authored
Bug: 951571 Change-Id: Ia7a1b79db063f1456e14411ea1bd086936577d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626847 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#663013}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/431ef2fdd373..d68aff6c7482 git log 431ef2fdd373..d68aff6c7482 --date=short --no-merges --format='%ad %ae %s' 2019-05-24 jiajia.qin@intel.com Fix the crash when the array size is not big enough. Created with: gclient setdep -r src/third_party/angle@d68aff6c7482 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=ynovikov@google.com Change-Id: I1ba9dfbffc369cdf78141035ee8bbec7da199334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628534Reviewed-by:
-
Friedrich Horschig authored
Instead of copying the string by using const base::string16& while constructing AccessorySheetData, pass base::string16 by value and move. Bug: None Change-Id: I012eb266cf5bed77df40c276b0eb49b3ac21c6e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624912Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#663011}
-
Kunihiko Sakamoto authored
Bug: 966753 Change-Id: I96ef53cffae46c0d69ce4c1240e6283075ea3228 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628629Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#663010}
-
Yuki Shiino authored
This reverts commit 0daefdcf. Reason for revert: DCHECK(!GetDocument()->LoadEventStillNeeded()); in local_frame.cc is failing at https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests%20%28dbg%29 Original change's description: > Frame freezing on load. > > Move load event checks to renderer side so it is consistent with the > page lifecycle spec. Add additional resource that is slow to load > to ensure the load event is waited for correctly before freezing. > > BUG=907125 > > Change-Id: I8f45ddffcf3ce88f6244307833325a54e1c2d395 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625464 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Dave Tapuska <dtapuska@chromium.org> > Cr-Commit-Position: refs/heads/master@{#662340} TBR=avi@chromium.org,haraken@chromium.org,dtapuska@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 907125 Change-Id: I4e27e30519359e2a3ef0d2c92a0fc9d88ac78aff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628499Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#663009}
-
Alexei Filippov authored
Change-Id: Ie940ec04243b1a4382cd557c8d9b462d6a2fab0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628250Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#663008}
-
Michael Lippautz authored
Increase live byte counter on transitioning an object from unmarked to marked state. This results in an accurate live byte counter after marking and even before sweeping is started. In future, this values is communicated to V8 to allow computing a global limit indicating when the next GC should be started. Performance-wise, this only shifts the accounting work from the sweeper to the marker. Both still run on the main thread. Delta in reland: - Fix and test for crasher when trying to adjust marked bytes. Bug: 948807, 966456 Change-Id: I2d92c530c8e4c3b2d054580df5daf1822be0aa86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627041 Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
-
Elly Fong-Jones authored
The rest of this code is going away too. Bug: None Change-Id: I4a3dc9d4a000ac9d9830e5e50d057085313ad1a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626537 Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#663006}
-
Johannes Kron authored
RTP timestamp was recently added to RTCRtpContributingSource in the WebRTC specification. This CL reflects that change. Bug: chromium:965994 Change-Id: Iba76a2b90547e7ca70bb04dd556914c7f36ea3fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625106 Commit-Queue: Johannes Kron <kron@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#663005}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b7f4af8aae5e..583fc3036847 Created with: gclient setdep -r src-internal@583fc3036847 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=yukishiino@google.com,lgrey@google.com,masonfreed@google.com,rsorokin@google.com Change-Id: I20f3c38dba278e7b35ab9df5a87ea15c94e09dd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628531Reviewed-by:
-
Wei Lee authored
This CL adds getCameraFacing() API for CCA to get camera facing. Bug: None Test: Manually Change-Id: Ic400ed3012416f6d22f61fb553f9a74e7a1c24dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624425Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Sheng-hao Tsao <shenghao@chromium.org> Reviewed-by:
Ricky Liang <jcliang@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#663003}
-
Kuo Jen Wei authored
Bug: 965933 Test: On HALv1 device the CCA function normally without resolution settings menu. On HALv3 device the CCA is able to capture with specified resolution from resolution settings menu. Change-Id: If22961c55a052a7a6061c62569d88aca69e332d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626063 Commit-Queue: Kuo Jen Wei <inker@chromium.org> Reviewed-by:
-
Ken Rockot authored
This adds an ack response to TracedProcess.ConnectToTracingService and defers internally registering the PID with PerfettoService until the ack is received. This ensures that an unresponsive or otherwise defunct service cannot indefinitely block tracing for other services in the same process. Also changes chrome_renderer instance registration back to a mode where it never reports a PID (as opposed to implicitly reporting its PID is the same as the browser's). This adheres to subtle but valid expectations in tracing code that services reporting a given PID are actually running in that process. Bug: 962918 Change-Id: I71273f8ba954f580c1375e9b0ce2ab6c148b69b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626991 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#663001}
-
Hayato Ito authored
This is a preparation CL for https://crrev.com/c/1628495 so that it has a nice diff. Bug: 623464 Change-Id: I3adcb0796ea619804f61a7cc2a69821300b2bf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628627 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by:
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=gbiv@chromium.org Change-Id: I87d46ce9b72344e72511a50ffba4668ba2c2e4c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628533Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/27ec91958501..66e46037d74f git log 27ec91958501..66e46037d74f --date=short --no-merges --format='%ad %ae %s' 2019-05-24 johnkslang@users.noreply.github.com Merge pull request #1772 from mattparks/patch-2 Created with: gclient setdep -r src/third_party/glslang/src@66e46037d74f The AutoRoll server is located here: https://autoroll.skia.org/r/glslang-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=radial-bots+chrome-roll@google.com,ynovikov@google.com Change-Id: I99b8c4a4190794072c0e1ebd07983137a5e6e61a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628549Reviewed-by:
-
Nikunj Bhagat authored
Change-Id: I4cd59c9a8e245ea3af4fcdb0bdd602f066c6fef0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610310Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Nik Bhagat <nikunjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#662997}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/8a2441d37d80..032c7152644d git log 8a2441d37d80..032c7152644d --date=short --no-merges --format='%ad %ae %s' 2019-05-24 swiftshader.regress@gmail.com Regres: Update test lists @ 8a2441d3 Created with: gclient setdep -r src/third_party/swiftshader@032c7152644d The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=swiftshader-team+autoroll@google.com Change-Id: I666a0b64a14fadd83a9e3dfd4988ac130b69ec29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628552Reviewed-by:
-
Dominic Battre authored
Bug: 966041 Change-Id: I4cdcf0b5631dd71004d162f77ef028f794e09eee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625119Reviewed-by:
Nik Bhagat <nikunjb@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#662995}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/65790b717589..441284b3fb3e git log 65790b717589..441284b3fb3e --date=short --no-merges --format='%ad %ae %s' 2019-05-24 dberris@chromium.org Pinpoint: align table header text left Created with: gclient setdep -r src/third_party/catapult@441284b3fb3e The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:966146 TBR=eyaich@google.com Change-Id: I1b824a2625c9b1fc6e9a418ffe078742f5305d0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628553Reviewed-by:
-
Danil Chapovalov authored
That allows to use chromium's implementation of the webrtc::TaskQueueFactory explicitly instead of through the global variable Bug: webrtc:10284 Change-Id: Id79d63fd9710d72cfe17497ef91b615999350cfe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627381Reviewed-by:
-
Hayato Ito authored
This is a preparation CL for https://crrev.com/c/1614723. As per the review comment [1], we can use FrameTreeNode id, instead of WebContentsGetter, in WebContentsGetterRegistry because we can get WebContentsGetter from FrameTreeNode id, as well as to know whether the frame is mainframe or not from the id. WebContentsGetterRegistry is now renamed to FrameTreeNodeIdRegistry. [1] https://crrev.com/c/chromium/src/+/1614723/12/content/browser/web_contents/web_contents_getter_registry.h#16 Bug: 623464 Change-Id: Ifab7727f6a6b74408f815e5b853d75d39c515f9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623611 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
-
Dominik Röttsches authored
Navigating to a URL and waiting for that to complete requires sync primitives. Change-Id: Iae111ac9ee2521de4054f82829f030f797cfaac4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627358Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#662991}
-
Timothy Loh authored
This reverts commit 38cccb45. Reason for revert: ExtensionWebRequestApiTest.WebSocketRequestAuthRequired failing on linux-chromeos-dbg non_network_service_browser_tests e.g. https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-dbg/12545 Original change's description: > [websocket] Split interface mojom::WebSocketClient > > This CL splits the interface to two parts so that WebRequestProxyingWebSocket or > extensions proxy only handshake of WebSocket: > > interface WebSocketHandshakeClient { > OnStartOpeningHandshake(WebSocketHandshakeRequest request); > OnFinishOpeningHandshake(WebSocketHandshakeResponse response); > OnAddChannelResponse(string selected_protocol, string extensions); > }; > > interface WebSocketClient { > OnDataFrame(bool fin, WebSocketMessageType type, array<uint8> data); > OnFlowControl(int64 quota); > OnDropChannel(bool was_clean, uint16 code, string reason); > OnClosingHandshake(); > OnFailChannel(string reason); > }; > > Performance gain of receive-arraybuffer-1MBx100.html: > Mine: 1050 ms > ToT : 1221 ms > > Bug: 865001, 942989 > Change-Id: Ia364afd96005a77b1dadf2c95896be5a12827f13 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599819 > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Reviewed-by: Ken Rockot <rockot@google.com> > Reviewed-by: Yutaka Hirano <yhirano@chromium.org> > Reviewed-by: Adam Rice <ricea@chromium.org> > Commit-Queue: Yoichi Osato <yoichio@chromium.org> > Cr-Commit-Position: refs/heads/master@{#662937} TBR=kinuko@chromium.org,ricea@chromium.org,rockot@google.com,yhirano@chromium.org,yoichio@chromium.org,karandeepb@chromium.org Change-Id: I8f974173d329d77258ba5b4ad45a4cb1f283bba0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 865001, 942989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628497Reviewed-by:
Timothy Loh <timloh@chromium.org> Commit-Queue: Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#662990}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ia4eb107dc89cf94a4d1462db8a731388270a18fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628548Reviewed-by:
-
Koji Ishii authored
This patch adds |PostLayoutChildren()|, and use it for the fix made at r661990 (crrev.com/c/1621796). When subtree layout occurs, ancestors of the subtree root may keep the reference to the old fragments. The new collection |PostLayoutChildren()| returns the latest fragments. Changing all uses of |Children()| to this does not work: 1. Some callers expect fragments being built during the layout, not the latest post-layout. Simply replacing breaks such callers. 2. This collection is not as fast as I wish it to be. Need to optimize/cache |IsRelayoutBoundary()| before using this in more performance critical work. 3. The best way to handle this situation isn't clear yet. Instead of this on-the-fly replacement, we may want to find all refences and patch them, as we tried in crrev.com/c/1622907. Maybe we need to support more generations. This is an architectual decision to be discussed more. This addition makes it easier to apply to other places if needed, and makes merging easier if we need to after the branch point, but where to apply is in future investigation. Bug: 965639 Change-Id: Idd4b539e88465cf0b810ae249fdcb87c0b19ae45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624010Reviewed-by:
Aleks Totic <atotic@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#662988}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/45750efbcdf2..b7f4af8aae5e Created with: gclient setdep -r src-internal@b7f4af8aae5e The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=lowell@google.com,kmilka@google.com,yutak@google.com Change-Id: I7af11b23662c4c33c1719319106420e44cda7f0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628264Reviewed-by:
-
Jay Harris authored
Bug: 906508 Change-Id: I7a1484874fd2afe1d7b4603b0de1ae6f20d08bbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624066 Commit-Queue: Jay Harris <harrisjay@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#662986}
-
Kuo Jen Wei authored
Bug: None Change-Id: Ifbbbe1ad0c5f50ea7454e1256b0ba8f9cdce2e55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624365Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e794ddc8a662..431ef2fdd373 git log e794ddc8a662..431ef2fdd373 --date=short --no-merges --format='%ad %ae %s' 2019-05-24 minkyu.jeong@samsung.com Add support for EXT_blend_minmax Created with: gclient setdep -r src/third_party/angle@431ef2fdd373 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=ynovikov@google.com Change-Id: I8a3c4976ac8d14931b8307fe1bb57ce662d5265e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628547Reviewed-by:
-
Tsuyoshi Horo authored
The existing SXG prefetch browsertests doesn't check the typical cross origin SXG loading behavior involving sender and distributor and publisher. This CL adds PrefetchedSignedExchangeCache_CrossOrigin, and PrefetchAlternativeSubresourceSXG_CrossOrigin tests. Bug: 935267 Change-Id: I3017c08c2096d2dba42227894db3519e542eae9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627846Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#662983}
-
Luciano Pacheco authored
Conversion done manually. Added static method "decorate" since it isn't using cr.ui.define anymore. This is the same idea used in FileTable, ComboButton, ProgressCenterItemElement and DirectoryTree. Manually tested "refresh" button triggering its command. Bug: 778674 Change-Id: Ib01207f6336d9f003d6c6d159ca4cc20ebab7e96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626843 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Commit-Queue: François Degros <fdegros@chromium.org> Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
François Degros <fdegros@chromium.org> Cr-Commit-Position: refs/heads/master@{#662982}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/c1c0d6d8ad74..316f3ac13b51 git log c1c0d6d8ad74..316f3ac13b51 --date=short --no-merges --format='%ad %ae %s' 2019-05-23 sukhanov@webrtc.org Datagram Transport Integration Created with: gclient setdep -r src/third_party/webrtc@316f3ac13b51 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I16523a8fc4f0f365f4a317eb003c655e4086e9c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627584Reviewed-by:
-
