- 29 Jun, 2018 40 commits
-
-
Tarun Bansal authored
Currently, Chromium disregards Accept-CH-Lifetime header on iframe navigation responses. This CL changes Chromium behavior to accept ACL header on iframe navigation responses provided the origin of the response matches the origin of the main frame navigation. This behavior is compliant with the updated client hints spec. WPT tests will come in a subsequent CL. Change-Id: I5603cad33f77d8e413b402b8a6c184497d87aec6 Bug: 856700 Reviewed-on: https://chromium-review.googlesource.com/1117859 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Yoav Weiss <yoav@yoav.ws> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#571438}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/7e2327b133db..723b1f6ef941 git log 7e2327b133db..723b1f6ef941 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 recipe-roller@chromium.org Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@723b1f6ef941 The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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=jcgregorio@chromium.org Change-Id: Icfc758485b0dd0dd775fa71d0fea86723b2277e2 Reviewed-on: https://chromium-review.googlesource.com/1119709Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571437}
-
Oscar Johansson authored
LogSeverity is a typedef in base/logging.h and a macro in the Windows header setupapi.h. When building using jumbo this causes a conflict. This commit solves the issue by undefining LogSeverity after importing setupapi.h. Bug: 850484,856964 Change-Id: I3e56c1a06357d8e03dbc98e01e51b18ae05e94dc Reviewed-on: https://chromium-review.googlesource.com/1116790Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Oscar Johansson <oscarj@opera.com> Cr-Commit-Position: refs/heads/master@{#571436}
-
Greg Kraynov authored
Also make RealTimeDomain internal. Bug: 783309 Change-Id: I142aa6f9c13bd6f5ce2211b95dd84a234fc71e0d Reviewed-on: https://chromium-review.googlesource.com/1118554 Commit-Queue: Greg Kraynov <kraynov@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#571435}
-
perfetto-chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/f1ba1dcd5882..da32244d8116 git log f1ba1dcd5882..da32244d8116 --date=short --no-merges --format='%ad %ae %s' 2018-06-28 michaschwab@google.com Create Canvas Wrapper Created with: gclient setdep -r src/third_party/perfetto@da32244d8116 The AutoRoll server is located here: https://perfetto-chromium-roll.skia.org 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=perfetto-bugs@google.com Change-Id: I7763e761b37c4efba08707c7c3388cfcc1fb57b5 Reviewed-on: https://chromium-review.googlesource.com/1119927 Reviewed-by: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571434}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/5fbb98122c59..20c3677acc37 git log 5fbb98122c59..20c3677acc37 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 thestig@chromium.org Revert "Simplify CPDF_PageOrganizer::UpdateReference method." Created with: gclient setdep -r src/third_party/pdfium@20c3677acc37 The AutoRoll server is located here: https://pdfium-roll.skia.org 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:858921,chromium:858952 TBR=dsinclair@chromium.org Change-Id: Idb479ee7ece0b0393389cbc86fe1a187b091207e Reviewed-on: https://chromium-review.googlesource.com/1119710Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571433}
-
Thomas Tangl authored
The following strings are updated as part of the transition to Unity: - the title of the sync setup and personalization page - sync section title and description - personalization title - unity master toggle title - Sign-in prompt title Mocks: https://gallery.googleplex.com/projects/MCHbtQVoQ2HCZWnUS9sdsb0Q/files/MCHtA7U1iMGr68-mD5nfi-3ML6EZ2WWTC08 TBR=dpapad@chromium.org Bug: 853187 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I3184c5e9c8614a1d7bdd900f346b19769e2c985d Reviewed-on: https://chromium-review.googlesource.com/1102501 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Reviewed-by:
Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#571432}
-
Takuto Ikuta authored
Now if we specify -fdebug-compilation-dir, clang-cl emits obj files independent from build directory. So this flag will allow to sharing build cache when engineers use goma on different build directory. To debug executable with this flag, we need to specify 'debug source files' property in visual studio. Some goma backend preparation for build cache sharing is on-going yet, but I will ask windows developer to try the flag to confirm it does not break their workflow. This is windows version of below proposal. https://docs.google.com/document/d/1OX4jY_bOCeNK7PNjVRuBQE9s6BQKS8XRNWGK8FEyh-E/edit?usp=sharing Bug: 712796 Change-Id: I65e6da67614839e5dde408038cad33a63dc28ac1 Reviewed-on: https://chromium-review.googlesource.com/1118200 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#571431}
-
Henrik Boström authored
This is in preparation for get/setParameters[1] and RTCRtpTransceiver[2]. Tests are updated to use promise_test and async/await to make them easier to write and to execute sequentially. Tests are updated to set up a call before getParameters() because many parameters are defined as "that has been negotiated". If we want to test what is returned before negotiation we should add that as separate tests. For now, this is necessary for the tests to run on [1][2]. Some tests are removed because they no longer reflect the spec. Because get/setParameters() and RTCRtpTransceiver has not landed yet, the tests are still expected to fail. [1] https://chromium-review.googlesource.com/c/chromium/src/+/1102436 [2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771 Bug: 803494, 777617 Change-Id: I3f14a37925837576a602d91bb67e48181c56a946 Reviewed-on: https://chromium-review.googlesource.com/1102502Reviewed-by:
Harald Alvestrand <hta@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#571430}
-
David Roger authored
When loading a token fails, kInvalidRefreshToken is used instead of the empty token. For such accounts, RefreshTokenIsAvailable() and RefreshTokenHasError() now return true. Change-Id: I0f206a183027162153b5a8de52e4c87c3462e84c Reviewed-on: https://chromium-review.googlesource.com/1107979Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#571429}
-
Erik Språng authored
The bitrate allocation class needs to be serialized in order to be passed over ipc. Also optimize the VideoBitrateAllocation to make it cheaper to get the sum, which is now being called in more and more places. Bug: chromium:853185 Change-Id: Id61fcfa5c5fe448cea0b1fef3283f3c414c7c5a4 Reviewed-on: https://chromium-review.googlesource.com/1102470Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Erik Språng <sprang@chromium.org> Cr-Commit-Position: refs/heads/master@{#571428}
-
Matthew Cary authored
Uses the new WritableUnalignedMapping class, which changes the ownership semantics. See the bug for details on the overall plan. Bug: 849207 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 Change-Id: Ie8da3246a5c7036322e72e120c4925cebc451f0e Reviewed-on: https://chromium-review.googlesource.com/1117685Reviewed-by:
Frank Liberato <liberato@chromium.org> Commit-Queue: Matthew Cary <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#571427}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/82d171c82469..776199a55a22 git log 82d171c82469..776199a55a22 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 mbonadei@webrtc.org Enable PeerConnectionEndToEndTest.CallWithLegacySdp on ASan. Created with: gclient setdep -r src/third_party/webrtc@776199a55a22 The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I1157cc6050b31b1867dea0575cf72c768a579fe1 Reviewed-on: https://chromium-review.googlesource.com/1119711Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571426}
-
Joel Hockey authored
Bug: 813477 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Iafe64af611275d2a434ad533c3c615a9ccb8abf5 Reviewed-on: https://chromium-review.googlesource.com/1119739 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Naoki Fukino <fukino@chromium.org> Cr-Commit-Position: refs/heads/master@{#571425}
-
Javier Fernandez authored
Flexible tracks should be considered as content-sized if the grid is laid out under indefinite size constraints. We only know this while running the track sizing algorithm for each direction, hence we should apply the same pattern for the Baseline Alignment offsets computation. Bug: 855568 Change-Id: Icfc9f3cefc70ab87004a772ac97b60e97b97249d Reviewed-on: https://chromium-review.googlesource.com/1113933 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#571424}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/898687843450..525fc9fdb588 git log 898687843450..525fc9fdb588 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 vapier@chromium.org cros_portage_upgrade: kill it for now 2018-06-29 vapier@chromium.org cros_portage_upgrade: switch to main repo for now Created with: gclient setdep -r src/third_party/chromite@525fc9fdb588 The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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:858925,chromium:858925 TBR=chrome-os-gardeners@chromium.org Change-Id: I9dc9d0b60f1aca280990bf58057f3e67a44fe37f Reviewed-on: https://chromium-review.googlesource.com/1119708Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571423}
-
Martin Kreichgauer authored
This changes the CredentialMetadata::EncodeRpId method to allow an RP ID to be recovered from the encoding, given the secret key; and it adds a CredentialMetadata::DecodeRpId method to do so. This is necessary because we need an effective way to test whether a given credential in the macOS keychain "belongs" to a given profile (i.e. was the metadata sealed/encoded under that profile's secret key), when performing browsing data deletion for that profile. This was previously impossible: Unsealing the credential ID requires the correct RP ID, with which the credential id ciphertext is authenticated. The other two fields (RP ID + user handle, and RP ID) are encoded with HMAC-SHA-256, so they are not reversible without the RP ID either. This CL changes the kSecAttrLabel field, which previously stored HMAC-SHA-256(rp_id), to store a deterministic encryption of rp_id instead. The cipher is AES-GCM-SIV with a fixed nonce. This makes the encoding reversible (because you can retrieve the RP ID by decrypting), while maintaining easy lookup of all credentials for a given RP (because the encoding is deterministic) and confidentiality (because you need the key to decrypt). Bug: 678128 Change-Id: I2e34ca5c7f28a2bd14a953539de6e0ac90568bec Reviewed-on: https://chromium-review.googlesource.com/1117609 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Adam Langley <agl@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#571422}
-
Ke He authored
This is the last step of servicification of geolocation. The whole //device/geolocation folder is moved to //services/device. The public files in //device/geolocation/public are moved to //service/device/public accordingly. BUG=800659 Change-Id: Id0413058874e20158f733e77c2eaed62f168f8ff Reviewed-on: https://chromium-review.googlesource.com/1102190 Commit-Queue: Ke He <ke.he@intel.com> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#571421}
-
chromeos-commit-bot@chromium.org authored
BUG=762641 TBR=xdai@google.com Change-Id: I15325bda1464dbcb9c2ec247943e2eca4fa5d7ee Reviewed-on: https://chromium-review.googlesource.com/1119423Reviewed-by:
ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#571420}
-
Tetsui Ohkubo authored
This CL moves remaining mojom::SystemTray implementation in SystemTrayController to SystemTrayModel, and changes SystemTrayModel to bind mojom::SystemTray interface directly. TEST=trybot pass BUG=none Change-Id: Ie73cd257e19a5230387058f45c57a771a32310cf Reviewed-on: https://chromium-review.googlesource.com/1107582 Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#571419}
-
Oscar Johansson authored
The macro ENDPOINT is defined inside namespaces in: net/third_party/quic/core/quic_connection.cc net/third_party/quic/core/quic_crypto_handshaker.cc net/third_party/quic/core/quic_crypto_stream.cc net/third_party/quic/core/quic_data_reader.cc net/third_party/quic/core/quic_framer.cc net/third_party/quic/core/quic_packet_creator.cc net/third_party/quic/core/quic_sent_packet_manager.cc net/third_party/quic/core/quic_session.cc net/third_party/quic/core/quic_spdy_stream.cc When building using jumbo these end up in the same namspace and conflict. This commit solves the issue by undefining the macro inside the namespace. Bug: 772146 Change-Id: Ie85920ac632dd90402afc2276ed30fff8609d9be Reviewed-on: https://chromium-review.googlesource.com/1118220Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Commit-Queue: Oscar Johansson <oscarj@opera.com> Cr-Commit-Position: refs/heads/master@{#571418}
-
Han Leon authored
This CL adds a function OnDestroyed() into EmbeddedWorkerInstance::Listener interface, so that ServiceWorkerRegisterJob can stop observing EmbeddedWorkerInstance once it's gone away. BUG=856969,856330 Change-Id: I3acc9143f9ea2f8f24ab0aac465f29f97fdf9906 Reviewed-on: https://chromium-review.googlesource.com/1118006 Commit-Queue: Han Leon <leon.han@intel.com> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#571417}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/0601d68ac85e..82d171c82469 git log 0601d68ac85e..82d171c82469 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 mbonadei@webrtc.org Skip PeerConnectionEndToEndTest.CallWithCustomCodec on Win ASan builds. 2018-06-28 peah@webrtc.org AEC3: Allow filter adaptation even though the estimated echo is saturated 2018-06-28 terelius@webrtc.org Port RtcEventLog encoder unittests to the new parser API. Created with: gclient setdep -r src/third_party/webrtc@82d171c82469 The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng BUG=chromium:None,chromium:857426 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I2dc160e12af018a946993c8cbb0055e44cd8e9b7 Reviewed-on: https://chromium-review.googlesource.com/1119707Reviewed-by:
-
Matt Falkenhagen authored
This adds UMA for start worker breakdown recorded from the renderer. The plan is to replace the UMA that's recorded on the browser based on IPCs from the renderer. Some motivations include: * Avoid skewing the metrics when the IPCs get delayed due to busy browser IO thread. * Avoid delaying end-to-end start time. Each IPC is a chance to get delayed, which delays end-to-end start time. * Simplify the code. The timing milestones are: * start * browser sent start worker IPC * renderer received start worker IPC * JavaScript evaluation on the worker thread started * JavaScript evaluation on the worker thread ended * end The current implementation does more things, e.g., after JS evaluation end it posts another task to itself and then sends the worker started IPC, but this is expected to be removed so it's not added as a milestone here. The UMA added includes: * Total startup time: ServiceWorker.StartTiming.Duration * Start to milestone: ServiceWorker.StartTiming.StartToReceivedStartWorker ServiceWorker.StartTiming.StartToScriptEvaluationEnd ServiceWorker.StartTiming.StartToScriptEvaluationStart ServiceWorker.StartTiming.StartToSentStartWorker * Each milestone: ServiceWorker.StartTiming.SentStartWorkerToReceivedStartWorker ServiceWorker.StartTiming.ReceivedStartWorkerToScriptEvaluationStart ServiceWorker.StartTiming.ScriptEvaluationStartToScriptEvaluationEnd ServiceWorker.StartTiming.ScriptEvaluationEndToEnd See also: https://docs.google.com/document/d/18LzAAO7YFTMc2v6Nrr1EPypXd9CDzSTQTUyMGUPZieQ/edit?usp=sharing Change-Id: Ic6d0de634ca160518bcd6600ec3b22aa067ab086 Bug: 855952 Reviewed-on: https://chromium-review.googlesource.com/1114565 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#571415}
-
Fady Samuel authored
Don't use the CompositorLock if surface synchronization is enabled. This was causing issues on telemetry bots where the CompositorLock was preventing the UI from submitting CompositorFrames for a long period of time and so input latency was very high. Before: https://pinpoint-dot-chromeperf.appspot.com/job/11675b9b240000 After: https://pinpoint-dot-chromeperf.appspot.com/job/152a7367240000 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: I95407531216b543fb4c192387bd67fe690bee0b4 Bug: 672962 Reviewed-on: https://chromium-review.googlesource.com/1119191 Commit-Queue: Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#571414}
-
Ramin Halavati authored
This reverts commit fb40db12. Reason for revert: crrev.com/c/1117264 got reverted, and this CL is based on that. Original change's description: > Roll traffic_annotation_auditor for Linux > > The new binary for traffic_annotation_auditor after the change in > crrev.com/c/1117264 is rolled. > > Bug: 856884 > Change-Id: Ief41cd698f8190b3642582a2ddabf15724f91a2f > TBR: georgesak@chromium.org > Reviewed-on: https://chromium-review.googlesource.com/1117682 > Reviewed-by: Ramin Halavati <rhalavati@chromium.org> > Commit-Queue: Ramin Halavati <rhalavati@chromium.org> > Cr-Commit-Position: refs/heads/master@{#571041} TBR=georgesak@chromium.org,rhalavati@chromium.org Change-Id: Idac821023b403db1d9182b54616bcc50904a8401 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 856884 Reviewed-on: https://chromium-review.googlesource.com/1119785 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#571413}
-
Ramin Halavati authored
This reverts commit 081bb19a. Reason for revert: crrev.com/c/1117264 got reverted, and this CL is based on that. Original change's description: > Roll traffic_annotation_auditor binary for Windows. > > The new binary for traffic_annotation_auditor after the change in > crrev.com/c/1117264 is rolled. > > Bug: 856884 > Change-Id: I76523df5e58ace767ac19c619c9bb32da5a25674 > TBR: georgesak@chromium.org > Reviewed-on: https://chromium-review.googlesource.com/1117686 > Reviewed-by: Ramin Halavati <rhalavati@chromium.org> > Commit-Queue: Ramin Halavati <rhalavati@chromium.org> > Cr-Commit-Position: refs/heads/master@{#571048} TBR=georgesak@chromium.org,rhalavati@chromium.org Change-Id: I2706aa14d74d1c858d6e53c2703baf55c041f340 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 856884 Reviewed-on: https://chromium-review.googlesource.com/1119805Reviewed-by:
-
depot-tools-chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/ae1f03388f7a..406de133efaf git log ae1f03388f7a..406de133efaf --date=short --no-merges --format='%ad %ae %s' 2018-06-29 yyanagisawa@chromium.org Add gclient_utils to InputAPI export. Created with: gclient setdep -r src/third_party/depot_tools@406de133efaf The AutoRoll server is located here: https://depot-tools-chromium-roll.skia.org 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=agable@chromium.org Change-Id: I4ebdc7e46587f7903d11d5a904aabd144869f54b Reviewed-on: https://chromium-review.googlesource.com/1119706Reviewed-by:
depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571411}
-
Joel Hockey authored
Fixes Error: webkitResolveLocalFileSystemURL not found: [filesystem:drive/team_drives] Bug: 813477 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I6979d279f6986dba4ff5cb0ee6ac63b8f4594bfd Reviewed-on: https://chromium-review.googlesource.com/1119733 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#571410}
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.skia.org 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_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: Ia4a739ea250766e1d1747d2b39d0d2f529e41fba Reviewed-on: https://chromium-review.googlesource.com/1119765Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571409}
-
Colin Blundell authored
The GCMAccountTracker unittest currently plays fast-and-loose with the notion of an "account ID", which can be either the Gaia ID or the email address for a given account depending on the platform. This is a blocker to porting GCMAccountTracker to use IdentityManager, as the IdentityManager test infrastructure deliberately makes a much more explicit and enforced separation between email address, Gaia ID, and account ID. This CL paves the way for that porting by changing the GCMAccountTracker unittest to be explicit about its usage of the email address, Gaia ID, and account ID of a given account. Interestingly, this change exposed an actual production bug (https://crbug.com/856170). Bug: 809923 Change-Id: I46e2f632bacd89ba55132255a95bcb089d4fb3c8 Reviewed-on: https://chromium-review.googlesource.com/1113548 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#571408}
-
Muyuan Li authored
TBR=dcheng@chromium.org,jamescook@chromium.org,msw@chromium.org,xiaohuic@chromium.org Original change's description: > assistant: filter out incognito windows in assistant screenshot. > > Per privacy requirement, incognito windows should not be included > in screenshot sent to assistant server. > > Bug: b/78193324 > Test: > ash_unittests --gtest_filter=AssistantControllerTest.Screenshot > browser_tests --gtest_filter=BrowserNonClientFrameViewAshTest.IncognitoMarkedAsAssistantBlocked* > > Change-Id: Idf55135959721d69414a1ec6fae396f9763ebe49 > Reviewed-on: https://chromium-review.googlesource.com/1114293 > Commit-Queue: Muyuan Li <muyuanli@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> > Reviewed-by: Michael Wasserman <msw@chromium.org> > Cr-Commit-Position: refs/heads/master@{#571385} Change-Id: Ieecafffe5f1e14971b3c07dc799323a29885de16 Reviewed-on: https://chromium-review.googlesource.com/1119766Reviewed-by:
Muyuan Li <muyuanli@chromium.org> Commit-Queue: Muyuan Li <muyuanli@chromium.org> Cr-Commit-Position: refs/heads/master@{#571407}
-
Patti authored
Currently, All Sites shows all origins in their raw format, which looks crowded and can be confusing to users. Use the host instead in most situations, displaying non-HTTPS schemes off to the side to easily differentiate from other hosts that may be the same. Note non-default ports will also be shown as part of the host. See a screenshot - https://bugs.chromium.org/p/chromium/issues/detail?id=835712#c12 Bug: 835712 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Id34ef01e3fe41cd428e5a97bbc4fc207dbe07d05 Reviewed-on: https://chromium-review.googlesource.com/1107579 Commit-Queue: Patti <patricialor@chromium.org> Reviewed-by:
Dave Schuyler <dschuyler@chromium.org> Reviewed-by:
Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#571406}
-
afdo-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 The AutoRoll server is located here: https://afdo-chromium-roll.skia.org 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: Ie62c720fcdce018d12a54d5b69ddf0f34d8c76a3 Reviewed-on: https://chromium-review.googlesource.com/1119767Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571405}
-
Kent Tamura authored
security_context.h is used in 3,100+ compilation units, and this CL reduces its pre-processed size from 3.10MB to 1.74MB. Bug: 242216 Change-Id: I0fe6dd82eea775853cfe23377f2803bd0f90b069 Reviewed-on: https://chromium-review.googlesource.com/1119613Reviewed-by:
Takayoshi Kochi <kochi@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#571404}
-
Reza.Zakerinasab authored
This change does the plumbing for ImageDecoder::HighBitDepthDecodingOption, which is required to differentiate the expected behavior from PNGImageDecoder. This is a partial CL toward supporting 16 bit PNG decode to half float backed bitmap. This CL does not change the behavior and does not contain any tests. Testing is covered in the main CL: chromium-review.googlesource.com/c/chromium/src/+/1079788. Bug: 839034 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ie6f34b866b1fbe09bd425bdbecd7fb9726cf9621 Reviewed-on: https://chromium-review.googlesource.com/1113506 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Reviewed-by:
Urvang Joshi <urvang@chromium.org> Cr-Commit-Position: refs/heads/master@{#571403}
-
John Abd-El-Malek authored
There was a race condition when the policy fetch request that's initiated in CloudPolicyTest::SetUpOnMainThread is cancelled becauase the test bodies start their own request (through RefreshPolicies). The first request seems to get the python test server in a bad state and it stops responding to requests afterwards. The fix is to skip issuing the first request by temporarily unregistering CloudPolicyRefreshScheduler. TBR=pmarko Bug: 858883 Change-Id: I8c158ab3dffc2f38a7712a6806f9b8d28efbcfdb Reviewed-on: https://chromium-review.googlesource.com/1119628 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#571402}
-
Kouhei Ueno authored
This CL follows signed exchange spec change: https://github.com/WICG/webpackage/commit/3903da6e Bug: 803774 Change-Id: If93b419488c166b1d8ec8a35b7a752a439d1cd7a Reviewed-on: https://chromium-review.googlesource.com/1114407Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
-
Esmael El-Moslimany authored
Changing the paper-button bg-color to white was too big of a change and would require reviewing all usages of paper-button to ensure that style bugs similar to the one found in cr-toast do not occur. The default paper-button bg-color will not be set. The bg-color of paper-button in the user-manager will be set to white. And for cr-toast, the bg-color will be set to transparent (including the hover state). Bug: 845576 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I5b7a513012c43e2da0163555c1a5d25e69cf8328 Reviewed-on: https://chromium-review.googlesource.com/1115354 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by:
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/6d97dd7fb70f..898687843450 git log 6d97dd7fb70f..898687843450 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 vapier@chromium.org gerrit: update old googlecode URLs Created with: gclient setdep -r src/third_party/chromite@898687843450 The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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=chrome-os-gardeners@chromium.org Change-Id: Ia948fd9c24c9d0a0c4b259ffc3f612467b7dc1ad Reviewed-on: https://chromium-review.googlesource.com/1119705Reviewed-by:
-
