- 28 Jul, 2018 30 commits
-
-
Takuto Ikuta authored
This is a part of effort to remove /wd4018 warning suppression. Master CL is https://chromium-review.googlesource.com/c/chromium/src/+/1152755 This CL was uploaded by git cl split. R=ortuno@chromium.org Bug: 868248, 588506 Change-Id: I6f381e608322431356681f57a315271dca409d83 Reviewed-on: https://chromium-review.googlesource.com/1152843Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#578899}
-
Peter Kasting authored
This is a reland of 8c35e22c Original change's description: > Add background tab colors and inactive images to the theme system. > > These will eventually be used for three purposes: > (1) To allow generating different background tab images from a common tint for > the inactive and incognito cases, thus allowing background tabs that blend > into the frame for custom themes. > (2) To allow autogenerating the background tab colors from the background tab > images, thus letting us autocalculate better tab text/separator/etc. colors. > (3) To allow theme authors to customize/override this behavior more precisely. > > Reasons (1) and (2) dictated the design here; reason (3) is basically a free > bonus. I thought about not making these resources overrideable by theme > authors, but there was some technical reason that turned out to not be easily > feasible, and there seems little reason to prevent it. > > This also allows us to read THEME_TAB_BACKGROUND_INCOGNITO on Mac (Views). > > This shouldn't result in a visual change on its own. > > Bug: 862664 > Change-Id: Icc57f78fd526d68b83c692fbac669a7371bb38ff > Reviewed-on: https://chromium-review.googlesource.com/1147869 > Commit-Queue: Peter Kasting <pkasting@chromium.org> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Reviewed-by: Evan Stade <estade@chromium.org> > Reviewed-by: Allen Bauer <kylixrd@chromium.org> > Reviewed-by: Bret Sepulveda <bsep@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578790} Bug: 862664 Change-Id: I341bbce16853095f17b2608a7639bf0fd105c2cc TBR: estade, oshima, bsep, kylixrd Reviewed-on: https://chromium-review.googlesource.com/1154148Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#578898}
-
Alexey Baskakov authored
This is a move-and-rename CL, no behavior changes. Results: - web_app_shortcut.h contains extension-independent stuff. - web_app_extension_shortcut.h contains extension-based code. - All shortcut-related code moved from shell_integration_linux.cc to web_app_shortcut_linux.cc (so no circular dependency on web_app.h) This CL untangles all circular dependencies listed in web_applications/BUILD.gn. Modernize: - Replace arraysize with base::size. - UTF8String -> SysNSStringToUTF8. - BindOnce. Bug: 862049 Change-Id: I9bf098d00f363aa8ed1a0c45514dc04cb9923e9e Reviewed-on: https://chromium-review.googlesource.com/1138042 Commit-Queue: Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#578897}
-
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/306b6c168dc7..5b3b5cc126a7 git log 306b6c168dc7..5b3b5cc126a7 --date=short --no-merges --format='%ad %ae %s' 2018-07-28 zmo@chromium.org Suppress more tests on Android for NVIDIA Shield TV bot. Created with: gclient setdep -r src/third_party/angle@5b3b5cc126a7 The AutoRoll server is located here: https://angle-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: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@chromium.org Change-Id: Idce15cae04293f8c304882fc94690016a281cd69 Reviewed-on: https://chromium-review.googlesource.com/1154168Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#578896}
-
Khushal authored
Currently skia is limited to ES 2.0 for GPU raster, also apply this limitation for OOP raster since we suspect this might be causing crashes on Adreno (TM) 405 devices. TBR=vollick@chromium.org R=piman@chromium.org Bug: 866613 Change-Id: Icd4ed5116a28a31e3b4ba2121955fa595d837f33 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Reviewed-on: https://chromium-review.googlesource.com/1083883 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#578895}
-
Sergey Ulanov authored
Previously runner scripts were capturing debug logs from test instance only after successful SSH connection to the test device. This made it hard to debug issues that break system boot (mainly after SDK updates). This CL sets SSH connect timeout to 5 seconds (previously there was no timeout) and updates Target._WaitUntilReady() to capture logs with loglistener while waiting for SSH connection. The logs are printed to the output after second failed connection attempt. Change-Id: I4b57d3a13f3baa520d9e7bdd08a6e6a9236e7ecc Reviewed-on: https://chromium-review.googlesource.com/1148939 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#578894}
-
Xunran Ding authored
Bug: 760102 Change-Id: I3811976622dcc06845ac970de7436d7f1fb6896e Reviewed-on: https://chromium-review.googlesource.com/1146122Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Xunran Ding <xunran.ding@samsung.com> Cr-Commit-Position: refs/heads/master@{#578893}
-
Zhenyao Mo authored
BUG=868596 TEST=GPU FYI TBR=kbr@chromium.org 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: I1e32c3dfa4a6b8ea07b92159793fe8749f6ae031 Reviewed-on: https://chromium-review.googlesource.com/1154042 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#578892}
-
Peter Collingbourne authored
This is a reland of e3971799 Fixed test failures under msan, which were caused by accessing memory which was uninitialized because the read was invalid. All such accesses are now protected with a validity check. Original change's description: > cc, gpu: Make serialization code bitness agnostic. > > With this change we use the same serialization regardless of whether > we are targeting a 32-bit or a 64-bit machine. > > Bug: 865796 > 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;master.tryserver.blink:linux_trusty_blink_rel > Change-Id: I7a9f0a3b5d25569693bb5efec73c3f5cd256c39b > Reviewed-on: https://chromium-review.googlesource.com/1139106 > Reviewed-by: Antoine Labour <piman@chromium.org> > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > Cr-Commit-Position: refs/heads/master@{#577038} Bug: 865796 Change-Id: Id9dae1d2e5e2389ce96574c917314d63f5de5494 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;master.tryserver.blink:linux_trusty_blink_rel Reviewed-on: https://chromium-review.googlesource.com/1152370Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#578891}
-
src-internal-chromium-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1d201c0289f2..131b85f314db Created with: gclient setdep -r src-internal@131b85f314db The AutoRoll server is located here: https://src-internal-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:828550 TBR=mmoss@chromium.org Change-Id: I6ee1d3fe40a13f0715c7aebfcece085b3c3b7cf6 Reviewed-on: https://chromium-review.googlesource.com/1153927Reviewed-by:
src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#578890}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/3e03eba0a7e2..ee78b5c0fb0f git log 3e03eba0a7e2..ee78b5c0fb0f --date=short --no-merges --format='%ad %ae %s' 2018-07-27 bhthompson@google.com Disable bvt-arc suite on quawks-paladin Created with: gclient setdep -r src/third_party/chromite@ee78b5c0fb0f 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. TBR=chrome-os-gardeners@chromium.org Change-Id: Ib492a2f76dd13cf95c705a874308aae13229b458 Reviewed-on: https://chromium-review.googlesource.com/1153293Reviewed-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@{#578889}
-
Sergey Ulanov authored
Some cleanups for the ui::PlatformWindowDelegate interface 1. Removed device_pixel_ratio parameter from OnAcceleratedWidgetAvailable. It wasn't used anywhere and the passed value was incorrect for most PlatformWindow implementations. 2. Removed OnAcceleratedWidgetDestroying() - it wasn't used anywhere. 3. Clarified OnAcceleratedWidgetDestroyed() should not to be called from destructor. It's only useful on Android. Wayland and scenic implementations were calling it incorrectly in destructor. This also fixes the crash in the attached bug. TBR=piman@chromium.org (trivial change in //gpu) Bug: 866729 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: I164888802c65295bd07d9aa8d882332bbacbdbd9 Reviewed-on: https://chromium-review.googlesource.com/1147754 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#578888}
-
Kyle Horimoto authored
Previously, the setup flow used fake data and did not actually perform setup. This CL integrates the WebUI dialog by: (1) Adding Mojo bindings to the dialog's WebUIController. (2) Adds externs for Mojo types to the Closure compiler pass. (3) Updates WebUI code to use Mojo JS bindings. Bug: 824568 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I53acbc227b9d965f9337fbbdb84c90e285665745 Reviewed-on: https://chromium-review.googlesource.com/1139222 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#578887}
-
Peter Kasting authored
This is a reland of ec2cd434 Original change's description: > Misc. cleanup to browser_theme_pack_unittest.cc; no functional change. > > * Add GetDefaultColor() mapping function to make it easy to fix DCHECKs due to > this code using raw _INCOGNITO color constants but > ThemeProperties::GetDefaultColor() not expecting them. This is the change > that led me to get annoyed and do all the other stuff here. > * Convert typedefs to type aliases. > * Add TP = ThemeProperties type alias for brevity. > * Use =default. > * Mark functions that don't touch member variables "static". > * Fix wrapping issues. > * Because the class here is so long, split it into declaration and definition > pieces so it's easier to see what's the API and what's helper functions. > * Make the API protected; make helpers private. > * Make data members private. Add a const accessor for the one member tests use. > > Bug: none > Change-Id: I4cc058bb29747cfa84835edbc5ce765401e14527 > Reviewed-on: https://chromium-review.googlesource.com/1152108 > Reviewed-by: Evan Stade <estade@chromium.org> > Commit-Queue: Peter Kasting <pkasting@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578775} Bug: none Change-Id: I0a6e9543722f886c2528700e457fd0ef0d75dccd TBR: estade Reviewed-on: https://chromium-review.googlesource.com/1154147Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#578886}
-
Johannes Henkel authored
Will use this in the InspectorDOMDebuggerAgent and elsewhere, since Keys() returns vector<WTF::String> and it's a bit inefficient / ugly to call .empty() on that. Change-Id: I99f9cb6024077bbc60ada38e46240ac602bf8669 Reviewed-on: https://chromium-review.googlesource.com/1154038Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#578885}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/c3bc69f238f5..80eb42ba9ee8 git log c3bc69f238f5..80eb42ba9ee8 --date=short --no-merges --format='%ad %ae %s' 2018-07-27 herb@google.com Take advantage of newly const ref text stack 2018-07-27 bsalomon@google.com Update .clang-format to handle Objective-C files Created with: gclient setdep -r src/third_party/skia@80eb42ba9ee8 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=benjaminwagner@chromium.org Change-Id: If52c64653b770d9c7ae838d446540b559116deff Reviewed-on: https://chromium-review.googlesource.com/1153928Reviewed-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@{#578884}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/e635e9807dab..865c199d93d8 git log e635e9807dab..865c199d93d8 --date=short --no-merges --format='%ad %ae %s' 2018-07-27 buildbot@webrtc.org Roll chromium_revision 75645bae..8c2846e5 (578612:578726) Created with: gclient setdep -r src/third_party/webrtc@865c199d93d8 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: I3d85f6ecdd4b0fa70cfe144d759f0d18772b8364 Reviewed-on: https://chromium-review.googlesource.com/1153929Reviewed-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@{#578883}
-
Alexander Alekseev authored
This Cl replaces static images with animations. Bug: 852038 Change-Id: Id58f69e4275231dc4b6491358d10a343f529fc2f Reviewed-on: https://chromium-review.googlesource.com/1153832 Commit-Queue: Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#578882}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/4f737a90..201a484d Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I78f7544261c08bc0fc81b869fe982c6d52caedd7 Reviewed-on: https://chromium-review.googlesource.com/1153984Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#578881}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/6146214d30ab..0415e02db77d git log 6146214d30ab..0415e02db77d --date=short --no-merges --format='%ad %ae %s' 2018-07-27 thestig@chromium.org Roll DEPS for testing corpus to 4e2bafc0. 2018-07-27 thestig@chromium.org Make pixel_tests pass on Windows 10. 2018-07-27 thestig@chromium.org Make pdfium_embeddertests pass on Windows 10. 2018-07-27 hinoka@google.com [cq.cfg] Flip CQ to LUCI 2018-07-27 tsepez@chromium.org Tag XFA data bound to V8 Objects. Created with: gclient setdep -r src/third_party/pdfium@0415e02db77d 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:828177,chromium:828177,chromium:828177,chromium:860896 TBR=dsinclair@chromium.org Change-Id: I2fdc495ac5cc8249ff9ac7bb61189292deeae037 Reviewed-on: https://chromium-review.googlesource.com/1154007Reviewed-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@{#578880}
-
Johannes Henkel authored
For reference the PR that introduced the new InspectorSessionState / InspectorAgentState / Fields was https://chromium-review.googlesource.com/c/chromium/src/+/1149201. Change-Id: I69c43a22b0a20a8badba5ae907ca23ed93610614 Reviewed-on: https://chromium-review.googlesource.com/1153296 Commit-Queue: Johannes Henkel <johannes@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#578879}
-
glevin authored
Bug: 865800 TEST: Disabled!! Change-Id: Ib4f9622e031ace72111cfbe6e1f5fead36905e8b Reviewed-on: https://chromium-review.googlesource.com/1153660 Commit-Queue: Greg Levin <glevin@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Cr-Commit-Position: refs/heads/master@{#578878}
-
Johannes Henkel authored
- InspectorWorkerAgent - InspectorTracingAgent - InspectorAnimationAgent - InspectorPageAgent (started earlier) For reference the PR that introduced the new InspectorSessionState / InspectorAgentState / Fields was https://chromium-review.googlesource.com/c/chromium/src/+/1149201. Change-Id: Id0e94a9c944341fa2c08dcb3d7bfb00c4b437614 Reviewed-on: https://chromium-review.googlesource.com/1152695Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#578877}
-
Xida Chen authored
Under paint-touchaction-rects, the new result is actually correct. This CL changes the expected.txt and mark this test pass. A new test is added to show that with PaintTouchActionRects, the result is correct with clipping. Bug: 853912 Change-Id: Id6138081e9a782333edc2911a9e9f53997f0b564 Reviewed-on: https://chromium-review.googlesource.com/1151709Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#578876}
-
Krishna Govind authored
R=abdulsyed@chromium.org Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ia22c42dc512988b686ff68ae4fbcde272d6eca7a Reviewed-on: https://chromium-review.googlesource.com/1154137Reviewed-by:
Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#578875}
-
Yuwei Huang authored
As discussed previously, people who care about mobile data usage can limit mobile data usage from the app, so we can remove the warning dialog for now and see if there is any feedback lamenting its loss. Bug: 868194 Change-Id: I3efb1adb10b4207c67605c68195d480fbe7a7b3a Reviewed-on: https://chromium-review.googlesource.com/1152547Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#578874}
-
Chase Phillips authored
Each WebIDBFactory has a bound mojo interface from the thread that created the WebIDBFactory instance. The previous code allowed for the main thread and worker threads to use a single instance. There is a call-time constraint that the caller be on the same thread as where the bind originally occurred. When the previous was always calling the mojo interface from the IO thread, the constraint was never violated. Since we want to remove the IO thread hopping, though, this exposes the violation. I'm fixing that by allowing each top- level Blink IdbFactory to own its own WebIDBFactory. Eventually as part of this cleanup effort IdbFactory and WebIDBFactory will merge into a single class and simplify more of this code. Bug: 717812 Change-Id: I9571f5703261f0d6afda9ad04946cb10e42ce0e8 Reviewed-on: https://chromium-review.googlesource.com/1150914 Commit-Queue: Chase Phillips <cmp@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#578873}
-
dpapad authored
polymer-css-build 0.1.2 -> 0.3.0-alpha.7 polymer-bundler 3.0.1 -> 3.1.1 crisper 2.0.2 -> 2.1.1 This is required for allowing Polymer 2 optimize_webui=true builds. Bug: 852069 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I69da071fcf6999c366f1d60070888afb7a662f4a Reviewed-on: https://chromium-review.googlesource.com/1142900 Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#578872}
-
Koji Ishii authored
This patch fixes ShapeResult::ComputePositionData, CachedPositionForOffset, and CachedOffsetForPosition for when multiple glyphs have a same character (cluster) index. Bug: 636993 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I862117d1ac19d7950306edc574be8f3e9b03ccc3 Reviewed-on: https://chromium-review.googlesource.com/1153068 Commit-Queue: Koji Ishii <kojii@chromium.org> Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#578871}
-
Renjie authored
Merge internal change: 206330851 Bug: 788385 Change-Id: I0a0823638aa9692024751a80e6470bb11ddfeb3c Reviewed-on: https://chromium-review.googlesource.com/1153387Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Commit-Queue: Renjie Tang <renjietang@chromium.org> Cr-Commit-Position: refs/heads/master@{#578870}
-
- 27 Jul, 2018 10 commits
-
-
Jordy Greenblatt authored
Toggle button that controls a given pref. The element uses the SettingsBooleanControlBehavior, which causes its behavior to parallel that of settings-toggle-button. However, the settings-toggle-button has a few disadvantages for the MultiDevice Settings UI use case that made it expedient to create this new element to use instead: (1) The settings-toggle-button is designed as an entire row (as opposed to just a toggle) and it does not allow a button to replace the feature toggle in the DOM. Because the type of user input varies depending on the state of the user's GAIA account, this UI would have either have to completely detach and reattach its items when they switched input types or else it would have to change the settings-toggle-button to allow it to detach or at least hide its toggle. (2) In order to match the pattern of the network-summary-item used for the Instant Tethering feature our items have SVG icons, which would require further refactoring of the settings-toggle-button to accommodate. (3) We need toggles to control the unified MultiDevice feature suite and toggles for individual features. The latter case requires more explanation and as a result has some identifying features that do not necessarily apprear in the former case. Bug: 824568 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I986382a8aac31781e3d27c1f44397ddb048761f4 Reviewed-on: https://chromium-review.googlesource.com/1149001 Commit-Queue: Jordy Greenblatt <jordynass@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#578869}
-
Daniel Murphy authored
This reverts commit 080fe17e. Reason for revert: The corruption is still there, but now failing on Windows. Bug: 865393 Original change's description: > [DOMStorage] Moving cached namespaces to std::map > > There has been a bunch of memory-corruption-smelling crashes around this > area. Changing the container to a std::map should give us more > information about where this is happening, and maybe cause it to crash > somewhere else. > > R=mek@chromium.org > > Bug: 845400,821371,857464 > Change-Id: Ife8cb10336a4f0752db89e2bca836ed873f7c711 > Reviewed-on: https://chromium-review.googlesource.com/1129849 > Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> > Commit-Queue: Daniel Murphy <dmurph@chromium.org> > Cr-Commit-Position: refs/heads/master@{#573452} TBR=dmurph@chromium.org,mek@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 845400, 821371, 857464 Change-Id: Ie120acf347713d9c6172f26082ed9b18c3cc38bc Reviewed-on: https://chromium-review.googlesource.com/1153987 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#578868}
-
Lu Chen authored
Record duration between page load and first click, and intervals between consecutive clicks. This timing information can help us analyze the available opportunities to perform preload (and other pre* mechanisms). Bug: 850624 Change-Id: I8924d6409ce5695e0d9eb56e9be87b7bf5bfc5c3 Reviewed-on: https://chromium-review.googlesource.com/1149415 Commit-Queue: Lu Chen <chelu@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#578867}
-
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/9bf86f07acd5..306b6c168dc7 git log 9bf86f07acd5..306b6c168dc7 --date=short --no-merges --format='%ad %ae %s' 2018-07-27 jmadill@chromium.org D3D11: Use angle::Result error pattern. 1/3 2018-07-27 geofflang@chromium.org Fix/supress issues with EGL images on Android. Created with: gclient setdep -r src/third_party/angle@306b6c168dc7 The AutoRoll server is located here: https://angle-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: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@chromium.org Change-Id: I01ee932f0a5415853216c178e2b860ba85be4ddf Reviewed-on: https://chromium-review.googlesource.com/1153767Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#578866}
-
Penny MacNeil authored
"display.dll" is a Windows system dll. This causes a clash in debug component builds. Change the GN output_name for the display component to "ui_display". Ref: crbug/818388 Test: chromium.gpu waterfall bot (debug component), or chromium.gpu.fyi. Change-Id: Ibdb41cb6841708c61893a0e05d00f5af17b583cd Reviewed-on: https://chromium-review.googlesource.com/1152099Reviewed-by:
Robert Liao <robliao@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Penny MacNeil <pennymac@chromium.org> Cr-Commit-Position: refs/heads/master@{#578865}
-
Kenneth Russell authored
It should be applied on all macOS versions, not just Sierra. This affects the following WebGL 2.0 conformance test: deqp/functional/gles3/shaderoperator/common_functions.html Tbr: kainino@chromium.org Bug: 820225 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: Ib0ff46c871d8ab74e56026aff96cd150e61a33d9 Reviewed-on: https://chromium-review.googlesource.com/1152452Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#578864}
-
Weiyong Yao authored
Bug: 867003 Change-Id: I2ef56eeafcee60f23fbd2d67fb3193eb9cd360d4 Reviewed-on: https://chromium-review.googlesource.com/1148694 Commit-Queue: Weiyong Yao <braveyao@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#578863}
-
Scott Violet authored
This reverts commit ec2cd434. Reason for revert: Reverting in hopes of fixing unit_tests on chromeos bot. This one will hopefully take. Sorry for so many reverts here. The chain of patches made it difficult. Original change's description: > Misc. cleanup to browser_theme_pack_unittest.cc; no functional change. > > * Add GetDefaultColor() mapping function to make it easy to fix DCHECKs due to > this code using raw _INCOGNITO color constants but > ThemeProperties::GetDefaultColor() not expecting them. This is the change > that led me to get annoyed and do all the other stuff here. > * Convert typedefs to type aliases. > * Add TP = ThemeProperties type alias for brevity. > * Use =default. > * Mark functions that don't touch member variables "static". > * Fix wrapping issues. > * Because the class here is so long, split it into declaration and definition > pieces so it's easier to see what's the API and what's helper functions. > * Make the API protected; make helpers private. > * Make data members private. Add a const accessor for the one member tests use. > > Bug: none > Change-Id: I4cc058bb29747cfa84835edbc5ce765401e14527 > Reviewed-on: https://chromium-review.googlesource.com/1152108 > Reviewed-by: Evan Stade <estade@chromium.org> > Commit-Queue: Peter Kasting <pkasting@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578775} TBR=pkasting@chromium.org,estade@chromium.org Change-Id: I2407b13ff9c69c240bb7479e21a515c17c1388b7 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: none Reviewed-on: https://chromium-review.googlesource.com/1153991Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#578862}
-
Scott Violet authored
This reverts commit 8c35e22c. Reason for revert: Reverting to fix unit_tests on chromeos bot. This is next in the chain. Ugh! Original change's description: > Add background tab colors and inactive images to the theme system. > > These will eventually be used for three purposes: > (1) To allow generating different background tab images from a common tint for > the inactive and incognito cases, thus allowing background tabs that blend > into the frame for custom themes. > (2) To allow autogenerating the background tab colors from the background tab > images, thus letting us autocalculate better tab text/separator/etc. colors. > (3) To allow theme authors to customize/override this behavior more precisely. > > Reasons (1) and (2) dictated the design here; reason (3) is basically a free > bonus. I thought about not making these resources overrideable by theme > authors, but there was some technical reason that turned out to not be easily > feasible, and there seems little reason to prevent it. > > This also allows us to read THEME_TAB_BACKGROUND_INCOGNITO on Mac (Views). > > This shouldn't result in a visual change on its own. > > Bug: 862664 > Change-Id: Icc57f78fd526d68b83c692fbac669a7371bb38ff > Reviewed-on: https://chromium-review.googlesource.com/1147869 > Commit-Queue: Peter Kasting <pkasting@chromium.org> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Reviewed-by: Evan Stade <estade@chromium.org> > Reviewed-by: Allen Bauer <kylixrd@chromium.org> > Reviewed-by: Bret Sepulveda <bsep@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578790} TBR=pkasting@chromium.org,oshima@chromium.org,estade@chromium.org,bsep@chromium.org,kylixrd@chromium.org Change-Id: I6abe212768916890c11aec28aac5fc96891ac695 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 862664 Reviewed-on: https://chromium-review.googlesource.com/1153990Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#578861}
-
Scott Violet authored
This reverts commit 3b7859cb. Reason for revert: Reverting in hopes of get unit_tests passing on chromeos bot. This appears to be next in the chain to revert. Original change's description: > Add background tab text colors for inactive and incognito windows. > > With the default behavior of Chrome being to not show a tab background, we want > to change themes to default to that as well, unless the theme author actually > supplies an image/color for this explicitly. To do this, we need to support > different tab text colors for the cases where the frame colors can vary. This > adds the framework for that support. > > Right now, the default is to use the same text colors in inactive windows as > active ones. > > This also gives themes that want normal and incognito windows to differ greatly > (as the built-in theme's does) the ability to implement that and still have > readable tab titles. > > Bug: 866672 > Change-Id: I032a72bc799d0675c517db10283513a30db23328 > Reviewed-on: https://chromium-review.googlesource.com/1152418 > Commit-Queue: Peter Kasting <pkasting@chromium.org> > Reviewed-by: Evan Stade <estade@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578807} TBR=pkasting@chromium.org,estade@chromium.org,bsep@chromium.org Change-Id: I5e3a5772cea3f7a0d3f790d27dcccc66c51cb161 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 866672 Reviewed-on: https://chromium-review.googlesource.com/1154067Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#578860}
-