- 29 Jul, 2019 40 commits
-
-
Nico Weber authored
We're on a very different toolchain nowadays; maybe this works now. Bug: 485542 Change-Id: I5adfd8758853f18c1825d80e2b183ac1da1136f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721079 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#681784}
-
Armando Miraglia authored
crrev.com/c/1708136 fixed a bug so that when a device is unplugged and it was either a 'default' or a 'communications' device, or both, an onended event is triggered. This is a follow-up CL to add tests for it. BUG=970153 Change-Id: Id7bbe6428ae4ac735fe9ac0762a12d41c1b87240 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722834 Commit-Queue: Armando Miraglia <armax@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#681783}
-
Tanmoy Mollik authored
Remove AccountAdder.addAccount usage and replace it with calls to SignUtils.openSettingsForAllAccounts. Bug: 842860 Change-Id: I9187b916f7a8805dcdd7c39d9fca2580bd7eac62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1712676Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Tanmoy Mollik <triploblastic@google.com> Cr-Commit-Position: refs/heads/master@{#681782}
-
Mohamed Amir Yosef authored
In PasswordStoreX migration_step_pref_ gets destroyed on the UI thread in PasswordStoreX::ShutdownOnUIThread() but there could be already a task posted in PasswordStoreX::UpdateMigrationToLoginDBStep() that would actually consume the destroyed pref. We should invalidate the weak pointer when destroying the migration_step_pref_ to make sure any posted tasks are preempted! Change-Id: I7af97af346c61d352e8a294ce4998e641c8f08f6 Bug: 988417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722841 Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Auto-Submit: Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#681781}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1587f23b8531..3fea07b44639 Created with: gclient setdep -r src-internal@3fea07b44639 The AutoRoll server is located here: https://skia-autoroll.corp.goog/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=jbudorick@google.com Bug: chromium:None Change-Id: I4d437e0c8819dbb86f806aab652a1c70ad409eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723839Reviewed-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@{#681780}
-
Mohamed Abdelhalim authored
This includes removing |pending_nav_entry_id_| from NavigationHandleImpl since it is always equal to the |nav_entry_id_| in NavigationRequest, and neither of them is modified after the creation of the handle. Removing the logic for initializing |reload_type_| and |restore_type_| in NavigationHandleImpl. This does not change the current behavior, since if the |pending_nav_entry_id_| was not 0, this means the |nav_entry_id_| is not 0, and we can simply initialize both |reload_type_| and |restore_type_| in NavigationRequest. Bug: 916537 Change-Id: Ia51aa8d64021e37d81ea20f6328b21315af6be9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715081 Commit-Queue: Mohamed Abdelhalim <zetamoo@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Lowell Manners <lowell@chromium.org> Cr-Commit-Position: refs/heads/master@{#681779}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/41b798cb4e1e..a0ddf25cee99 git log 41b798cb4e1e..a0ddf25cee99 --date=short --no-merges --format='%ad %ae %s' 2019-07-29 treehugger-gerrit@google.com Merge "trace_processor: add tracks table" 2019-07-29 fmayer@google.com Merge "Dump on StopDataSource rather than on Flush." 2019-07-29 skyostil@google.com Merge "client api: Add a way to trace directly to a file" Created with: gclient setdep -r src/third_party/perfetto@a0ddf25cee99 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com Bug: None Change-Id: I9b8f428cfbf0961bada0b4639059dee07c5325b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724147Reviewed-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@{#681778}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ce4a26a406d3..ef732c88ba08 git log ce4a26a406d3..ef732c88ba08 --date=short --no-merges --format='%ad %ae %s' 2019-07-29 perezju@chromium.org [Telemetry] Fix typo in InvalidOptionsError message Created with: gclient setdep -r src/third_party/catapult@ef732c88ba08 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 TBR=simonhatch@google.com Bug: chromium:985712 Change-Id: Ib92aeeb0261891aa579404b0ca1c32dd6b1223f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724110Reviewed-by:
-
Marc Treib authored
After https://crrev.com/c/1642551 this is dead code. Bug: 836718 Change-Id: I6d429f0addaa201876a7fd6c574bb21180b8aef5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719491Reviewed-by:
Maxim Kolosovskiy <kolos@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#681776}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9789d9e4..6d7e1dd2 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ib181e387ecefab66e0419d84d9add06e009145f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723512Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#681775}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/fd6d8d7129ee..ed0febf57383 git log fd6d8d7129ee..ed0febf57383 --date=short --no-merges --format='%ad %ae %s' 2019-07-29 srte@webrtc.org Add k prefix to FrameGenerator::OutputType enum values 2019-07-27 bryanf@microsoft.com Allow use of CroppingWindowCapturer via CreateWindowCapturer Created with: gclient setdep -r src/third_party/webrtc@ed0febf57383 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 Bug: None Change-Id: Id4d20c4decf579ff32104f7f6f52c40e35a2f3cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724111Reviewed-by:
-
Lutz Justen authored
Disables org.chromium.chrome.browser.sync.ManageSyncPreferencesTest #testPaymentsIntegrationCheckboxEnablesPaymentsIntegration on Android. It's flaky on Nexus 5 devices. TBR=triploblastic@chromium.org,sahel@chromium.org BUG=chromium:987827 TEST=None Change-Id: If5bc156d28dc19f34d6bf2cf13e10ddb2d4ff4a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722961 Commit-Queue: Lutz Justen <ljusten@chromium.org> Reviewed-by:Lutz Justen <ljusten@chromium.org> Cr-Commit-Position: refs/heads/master@{#681773}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/d7e0a36ac618..c405776eb4a0 git log d7e0a36ac618..c405776eb4a0 --date=short --no-merges --format='%ad %ae %s' 2019-07-29 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/glslang/src 42f813401bdf..7fc868349143 (2 commits) Created with: gclient setdep -r src/third_party/angle@c405776eb4a0 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=geofflang@google.com Bug: chromium:None Change-Id: I34253ba09aed85e367d13a6c0659d732db12bab7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723088Reviewed-by:
-
Nazerke authored
Bug: 976660. Change-Id: I2b97ebca86494d41b27b29c696eddd75a26f9f67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715278 Commit-Queue: Nazerke Kalidolda <nazerke@google.com> Auto-Submit: Nazerke Kalidolda <nazerke@google.com> Reviewed-by:
Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#681771}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/ae9673f68e84..41b798cb4e1e git log ae9673f68e84..41b798cb4e1e --date=short --no-merges --format='%ad %ae %s' 2019-07-29 fmayer@google.com Merge "Count invalid packets in TraceStats." Created with: gclient setdep -r src/third_party/perfetto@41b798cb4e1e The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com Bug: None Change-Id: Iac6f580f3108a160f2fe1d6064f56a9b123254a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723087Reviewed-by:
-
Gabriel Charette authored
Also renamed the types to "Functions" instead of "Callbacks" as the latter is confusing with a properly bound base::Callback where the former clearly denotates a function pointer. This lack of initialization resulted in an access violation instead of using the non-overridden function when tracing is called in contexts where the perfetto override isn't in place yet as part of https://chromium-review.googlesource.com/c/chromium/src/+/1680893 We were simply lucky to get away with until now. R=eseckler@chromium.org Bug: 899897 Change-Id: I815fe5197888c32200cdf5166a0be4fbf79d355a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721071 Auto-Submit: Gabriel Charette <gab@chromium.org> Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#681769}
-
Maksim Sisov authored
This reverts commit 6f370b54. Reason for revert: the CL[1], which resulted in the problem, was reverted. Thus, there is no need to have this anymore. I will keep my eye on the issue and report again if anything. [1] https://crrev.com/c/1685909 Original change's description: > Disable partial swap for gl es type of gl > > Currently, partial swap is disabled on Linux with Mesa drivers and > with gl_type: gl. > > Likely, we could not experience any glitches crrev.com/c/1685909, > but once that CL has been merged, partial swap became broken on > Mesa with OpenGL ES (which Wayland uses). Not sure why it started > to happen, but I can assume that the problem is in the Mesa impl > for Wayland as well. Even though, the spec says Wayland compositor > updates only that part of a surface, which has damage, other parts > of a surface showing black squares. > > One reason behind that might be missing EGL_NV_post_sub_buffer > extension, which we can't test while being in the GPU process > when dma buffers are used. It is required to create an egl > surface to test against that extension. However, the spec > does not say anything about that. Ideally, Wayland compositor > must handle that by itself, make a union of damages and copy > parts of backbuffer to frontbuffer without getting OpenGL > into play, but something bad happens. At this point, > the problem has only been spotted on Mesa drivers. Others > will be tested asap. > > Thus, remove the gl type and enforce the workaround for both > Mesa with OpenGL and OpenGL ES. > > Bug: 983933 > Change-Id: I159627e95f854053956914f57e6299289ef04a74 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1705794 > Commit-Queue: Maksim Sisov <msisov@igalia.com> > Reviewed-by: Antoine Labour <piman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#679066} TBR=piman@chromium.org,msisov@igalia.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 983933 Change-Id: Ifadfe27b06c60032753b2a72d43305c622f2f8f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722839Reviewed-by:
Maksim Sisov <msisov@igalia.com> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#681768}
-
Lutz Justen authored
TBR=devlin@chromium.org BUG=chromium:988160 TEST=None Change-Id: Idabe57df448c82dcc596c5e1587ea446984e34ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724075Reviewed-by:
-
A Olsen authored
Trying to change the cryptohome password but supplying the wrong old password, can result in an "OnPasswordChangeDetected" instead of an OnAuthFailure. So, detect either one and treat them both as "incorrect old password", prompting the user to try again. Bug: 930109 Change-Id: I9aae5a52e377215f55ea0f788ff0ffacd2118865 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724076Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: A Olsen <olsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#681766}
-
Stephane Zermatten authored
This change fixes the following small bugs: - the argument experiment_ids was not declared for the list_assistant_actions direct action. - there was no way for the caller to specify the user account to use for RPCs, like there is for AA in CCT, which could mean RPCs could fail with 401 in production if the user is not signed into Chrome. list_assistant_actions now has a new parameter for that. - AutofillAssistantPreferencesUtil.isAutofillAssistantSwitchOn() was checked too early, when creating direct action handler, that is, when creating the Activity. This meant that if it ever changed during the Activity's lifetime, the behavior would be incorrect. This change checks it for every call instead. - If, after showing the onboarding, AA couldn't start, we could end up in a state where the onboarding UI was still showing. To solve this, this change transfers control of the UI only once AA is started. If that doesn't happen, the default behavior of OnboardingController triggers, which is to dismiss the UI. Bug: b/138276953 Change-Id: Ibd6ea42c710dc95fb854eea57d5a0b64a585573d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720711Reviewed-by:
Jordan Demeulenaere <jdemeulenaere@chromium.org> Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Cr-Commit-Position: refs/heads/master@{#681765}
-
Ivana Zuzic authored
Save action is a prerequisite for the future commit that will save the changes made on the password. Bug: 377410 Change-Id: I6482ad013a9fb1acc909a461ceb623f7d809cb3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710315Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Ivana Zuzic <izuzic@google.com> Cr-Commit-Position: refs/heads/master@{#681764}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/b110acba9e6f..12af46b649fd git log b110acba9e6f..12af46b649fd --date=short --no-merges --format='%ad %ae %s' 2019-07-24 apodtele@gmail.com * src/base/ftbbox.c (cubic_peak): Sanitize left shift (#56586). 2019-07-22 w1w2y3@gmail.com * src/cid/cidload.c (cid_hex_to_binary): Fix typo (#56653). Created with: gclient setdep -r src/third_party/freetype/src@12af46b649fd The AutoRoll server is located here: https://autoroll.skia.org/r/freetype-chromium 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_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:mac10.13_retina-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel TBR=bungeman@google.com,drott@google.com,thestig@google.com Bug: None Change-Id: Ice0b7783bb7ea08060e33737791c764ce931c6b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716394Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#681763}
-
Colin Blundell authored
Bug: 970295 Change-Id: I814a69f8e1c841cb0e58253382a568074414d62a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1718967 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
-
Victor Hugo Vianna Silva authored
We introduce a feature that when enabled will stop sync from registering controllers for FAVICON_IMAGE and FAVICON_TRACKING data types. Bug: 978775 Change-Id: I8739e001a639c6ab31d4bba51a42c83b69129b61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653428 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#681761}
-
Raphael Kubo da Costa authored
When building HarfBuzz as part of Chromium, there is a single source set with all the files we need in the build. Upstream HarfBuzz, on the other hand, produces a few different libraries: harfbuzz, harfbuzz-icu and harfbuzz-subset. When |use_system_harfbuzz| is true, we were only looking for (and using) harfbuzz.pc with pkg-config even though we also use symbols from libharfbuzz-subset.so. This resulted in errors when linking: ld: obj/skia/skia/SkPDFSubsetFont.o: in function `SkPDFSubsetFont(sk_sp<SkData>, SkPDFGlyphUse const&, SkPDF::Metadata::Subsetter, char const*, int)': SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x48a): undefined reference to `hb_subset_input_create_or_fail' ld: SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x4af): undefined reference to `hb_subset_input_glyph_set' ld: SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x5d7): undefined reference to `hb_subset_input_set_retain_gids' ld: SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x5e4): undefined reference to `hb_subset_input_set_drop_hints' ld: SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x5f3): undefined reference to `hb_subset' ld: SkPDFSubsetFont.cpp:(.text._Z15SkPDFSubsetFont5sk_spI6SkDataERK13SkPDFGlyphUseN5SkPDF8Metadata9SubsetterEPKci+0x66f): undefined reference to `hb_subset_input_destroy' as reported in https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/UyJsVJ5QqWo/jSv5z7-rEQAJ Change-Id: I997af075c7b7263cd7cc71a63db5b0f93bd1ab59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715288 Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: Dominik Röttsches <drott@chromium.org> Reviewed-by: -
Rune Lillesveen authored
Bug: 972752 Change-Id: I61ae4496ac0438e3ebf192dd3f44550e6862748c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722949Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#681759}
-
Stephen Nusko authored
This ensures that all data sources are restarted properly before stopping the trace which ensures we don't look like we're dropping data. In addition make the APILevel test completely self contained in the function to prevent state leakage. Bug: 987419 Change-Id: I026f09efae2f600ed2af7f3c663b78f9ee616890 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716754 Commit-Queue: Stephen Nusko <nuskos@chromium.org> Auto-Submit: Stephen Nusko <nuskos@chromium.org> Reviewed-by:
-
Mohamed Abdelhalim authored
This includes removing the related functions, and in-lining them in NavigationRequest instead. Bug: 916537 Change-Id: I6c7ca57d533a43067607dc761469738702374669 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720835Reviewed-by:
-
Koji Ishii authored
This patch changes ParseCacheControlDirectives() to use LowerASCII instead of DeprecatedLower. DeprecatedLower has partial Unicode conversions, such as converting U+212A to 'k', but lowering only ASCII should be sufficient for most web platform usages. Currently, there are 6 usages of AtomicString::DeprecatedLower and 37 usages of String::DeprecatedLower. This patch reduces one of the 6 usages. Bug: 627682 Change-Id: Ib48c430d7afe3e16be5dc567593b7f4b2634c4e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721210 Auto-Submit: Koji Ishii <kojii@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#681756}
-
Anders Hartvoll Ruud authored
This verifies that a reference to a cycle or 'guaranteed-invalid value' [1] behaves as 'unset' for custom properties registered with inherits=true. We already have tests that verify the same for inherits=false, but the inherits=true case is important to check that we're actually using 'unset' behavior, and not 'initial' behavior. [1] https://drafts.csswg.org/css-variables/#guaranteed-invalid Bug: 980930 Change-Id: I1c478f65eeca6b528766ebe023a7179442263285 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722836Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#681755}
-
François Beaufort authored
WebGPU spec says GPUTextureDescriptor.size is required when creating a texture. Bug: 877147 Change-Id: Ie0f68f7dd54c55b6d4aab826dc52274af386b54e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724090 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Auto-Submit: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#681754}
-
Balazs Engedy authored
Add engedy@ and hkamila@, and remove alumni. Bug: None Change-Id: I8a8e8b0c2c33cbe7d7241fa5cecff52fcb5ea097 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1718965 Auto-Submit: Balazs Engedy <engedy@chromium.org> Reviewed-by:
Raymes Khoury <raymes@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#681753}
-
Leon Han authored
This CL renames the wpt test NFCReader.html to NFCReader.https.html because WebNFC API is available only in secure contexts, then fixes the code to make it pass. BUG=520391 Change-Id: Id8f584c7ced901f15b087aec5f96fd83ba8f6d68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720154Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Leon Han <leon.han@intel.com> Cr-Commit-Position: refs/heads/master@{#681752}
-
Victor Hugo Vianna Silva authored
Currently LargeIconService allows callers to decide the size of the favicon they wish to download from the favicon server. Depending on which UI surface the user opens first, a different size is downloaded, which can cause displaying upscaled icons and decrease in quality. We solve this by downloading a single sufficiently big size (chosen based on existing values used by callers), aiming to only have downscaling. Bug: 982810 Change-Id: Ibad636d4c4d63791e9eb62d99221d9f35c9cb375 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695268 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Kristi Park <kristipark@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Reviewed-by:
Nicolas Zea <zea@chromium.org> Cr-Commit-Position: refs/heads/master@{#681751}
-
Yutaka Hirano authored
...with a StrongAlias. StrongAlias is now recommended for replacing bool params. Discussion: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GF1Wg0JbEhw Bug: None Change-Id: Ic9d31b68f0ead9609997dd6c5c430134dea7d85d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722467 Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Auto-Submit: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#681750}
-
Matthew Cary authored
This replaces a legacy base::SharedMemory member with a base::UnsafeSharedMemoryRegion and base::WritableMemoryMapping pair. Functionality is unchanged, other than having separate error messages for failure on region creation and region mapping. Bug: 849207 Change-Id: I7f0123fddb02aa6f1cd093d1c142a780728822e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697601Reviewed-by:
Ricky Liang <jcliang@chromium.org> Commit-Queue: Matthew Cary (CET) <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#681749}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/f54b8653dd9d..9559cdbdf011 git log f54b8653dd9d..9559cdbdf011 --date=short --no-merges --format='%ad %ae %s' 2019-07-26 dnovillo@google.com Fix #2609 - Handle out-of-bounds scalar replacements. (#2767) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@9559cdbdf011 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel;luci.chromium.try:win_angle_deqp_rel_ng TBR=radial-bots+chrome-roll@google.com,geofflang@google.com Bug: None Change-Id: I289bd7cf9b2b847ace74c7fb9ec19a5e1a4ac890 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723836Reviewed-by:
-
Monica Basta authored
Add a histogram to record the value of |kTokenServiceDiceCompatible| preference on every startup. Bug: 983983 Change-Id: I47ce649509cd4c50a498540e5efa2d241de74043 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719352Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Commit-Queue: Monica Basta <msalama@google.com> Cr-Commit-Position: refs/heads/master@{#681747}
-
Marc Treib authored
The corresponding data types have been migrated to USS, which uses GROUP_NON_BLOCKING (which essentially means "don't use a ModelSafeWorker at all"). So the workers for FILE and HISTORY were still instantiated, but never actually used. This also lets us remove the whole HistoryModelWorker class. TBR=sky for trivial updates to components/history/core/browser/BUILD.gn (removing the deleted sync files). Bug: 923287 Change-Id: Ief4ed46fce41346ea35ea46535b8d06d6c4d212e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720709 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/a96b79f90940..d7e0a36ac618 git log a96b79f90940..d7e0a36ac618 --date=short --no-merges --format='%ad %ae %s' 2019-07-29 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src f54b8653dd9d..9559cdbdf011 (1 commits) Created with: gclient setdep -r src/third_party/angle@d7e0a36ac618 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=geofflang@google.com Bug: chromium:None Change-Id: I7a9e5eef47c20950397751d69e3f3b8040620f55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723837Reviewed-by:
-
