- 17 Jul, 2018 40 commits
-
-
Brian Osman authored
This enum is going away, and is always assumed to be kIgnore within Skia. Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I1d330478aab486864395ef36762f12f3df76c4d2 Reviewed-on: https://chromium-review.googlesource.com/1135551Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Oliver Chang <ochang@chromium.org> Reviewed-by:
Mike Klein <mtklein@chromium.org> Commit-Queue: Brian Osman <brianosman@google.com> Cr-Commit-Position: refs/heads/master@{#575614}
-
Ramin Halavati authored
The default storage for OverlayUserPrefStore which is used for incognito preferences is the persistent storage in the regular profile, and preference types that should not be stored there must be enumerated in CreateIncognitoPrefServiceSyncable. This is changed so that the default storage is in memory, and preferences that need a persistent storage would need enumeration. Bug: 861722 Change-Id: Ia4c8f655752a07f81fb6d35685876cd252118999 Reviewed-on: https://chromium-review.googlesource.com/1128753 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Jonathan Ross <jonross@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#575613}
-
Greg Kraynov authored
Long live base::TestMockTimeTaskRunner. Bug: 863350 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Id3df59c1fb1588e95e0135c7c6a90cfad47d29f1 Reviewed-on: https://chromium-review.googlesource.com/1140062 Commit-Queue: Greg Kraynov <kraynov@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#575612}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/f1b3e80f..dcf3638e 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: I2a8194643473bf816ddc6aa84c362e4a747cb058 Reviewed-on: https://chromium-review.googlesource.com/1139909Reviewed-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@{#575611}
-
Greg Kraynov authored
Bug: 863350 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I74b5ab9428ec1b5452c374f4c9dccea7e26612ab Reviewed-on: https://chromium-review.googlesource.com/1138313 Commit-Queue: Greg Kraynov <kraynov@chromium.org> Reviewed-by:
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/bf2a980d03db..9c98576bceff git log bf2a980d03db..9c98576bceff --date=short --no-merges --format='%ad %ae %s' 2018-07-17 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 e076a2327f0d..6fb8ba4e8660 (3 commits) Created with: gclient setdep -r src/third_party/skia@9c98576bceff 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=bungeman@chromium.org Change-Id: I47ccd1d1e1c0745e7f8b2185ad2152b39331d02d Reviewed-on: https://chromium-review.googlesource.com/1139915Reviewed-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@{#575609}
-
Raphael Kubo da Costa authored
skcms' Transform_inl.h assumes support for 16-bit floating point in the __ARM_FP macro means the __fp16 (and corresponding SIMD data type) is present. While this is currently true for LLVM, which always sets the equivalent of GCC's -mfp16-format=ieee internally on ARM builds, GCC explicitly needs that option to be specified in order to enable support for __fp16. Doing so allows GCC ARM builds to proceed without the following error: ../../third_party/skia/third_party/skcms/src/Transform_inl.h: In function 'F_from_Half_': ../../third_party/skia/third_party/skcms/src/Transform_inl.h:101:72: error: 'float16x4_t' undeclared (first use in this function); did you mean 'float32x4_t'? SI ATTR F NS(F_from_Half_(U16 half)) { return vcvt_f32_f16((float16x4_t)half); } ^~~~~~~~~~~ float32x4_t ../../third_party/skia/third_party/skcms/src/Transform_inl.h:101:72: note: each undeclared identifier is reported only once for each function it appears in ../../third_party/skia/third_party/skcms/src/Transform_inl.h:101:84: error: expected ')' before 'half' SI ATTR F NS(F_from_Half_(U16 half)) { return vcvt_f32_f16((float16x4_t)half); } ^~~~ ) ../../third_party/skia/third_party/skcms/src/Transform_inl.h: In function 'Half_from_F_': ../../third_party/skia/third_party/skcms/src/Transform_inl.h:102:5: error: can't convert a value of type 'int' to vector type '__vector(4) short unsigned int' which has different size SI ATTR U16 NS(Half_from_F_(F f)) { return (U16)vcvt_f16_f32( f); } ^~ Bug: 819294 Change-Id: Ib7417fb9bdc6bd93553084053ba69f9d3409b112 Reviewed-on: https://chromium-review.googlesource.com/1138251Reviewed-by: -
Ulan Degenbaev authored
This is a follow-up to 199e61ec. Bug: 850921 Change-Id: Icabee6ab7f196b3a59bf3b541aa9bc698f636386 Reviewed-on: https://chromium-review.googlesource.com/1140056Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#575607}
-
Justin Cohen authored
Bug: 859440 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I28b4542d8752d3c8ee52f62aa2894dabf787a0d7 Reviewed-on: https://chromium-review.googlesource.com/1139606Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#575606}
-
Justin Cohen authored
Bug: 859555 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I6c4c564f12ee0acb89fdcc9538f89e4277f1461a Reviewed-on: https://chromium-review.googlesource.com/1139528Reviewed-by:
-
Wez authored
We no longer define OS_POSIX under Fuchsia, so the !OS_FUCHSIA part of these conditionals is no longer required. TBR: jsbell, gab, thestig, rockot, kbr, sergeyu, skyostil, fdegans, alexmos, asanka Bug: 854721 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: Ia35a44036d520a6b5104ac3ee12f5469cbaf457f Reviewed-on: https://chromium-review.googlesource.com/1135898 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Reviewed-by:
-
jdoerrie authored
Similarly to r574552 this change moves the map of descriptors from the platform implementations to the BluetoothRemoteGattCharacteristic base class. In addition, default implementations for GetDescriptor() and GetDescriptors() are provided. Lastly, this change cleans up a few lint errors, mostly missing includes. Bug: 821766 Change-Id: Iada71c198d241acf3bddcc1414ff89aa150c1c84 Reviewed-on: https://chromium-review.googlesource.com/1136296Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#575603}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/0c5d09a8e978..9e945c84d2be git log 0c5d09a8e978..9e945c84d2be --date=short --no-merges --format='%ad %ae %s' 2018-07-17 manojgupta@google.com cros_chrome_sdk: Use cros nm for target builds. Created with: gclient setdep -r src/third_party/chromite@9e945c84d2be 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: I728eb50ce12cb807ca24f04ae25cffd769e7d57a Reviewed-on: https://chromium-review.googlesource.com/1139916Reviewed-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@{#575602}
-
Leszek Swirski authored
Bug: chromium:823663 Change-Id: I228aab31b4f152e0edc8310d3f4674a7f2022964 Reviewed-on: https://chromium-review.googlesource.com/1138617Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#575601}
-
Rakina Zata Amni authored
We previously implemented constructable CSSStyleSheet synchronously, but discussions in https://github.com/WICG/construct-stylesheets/issues/2 have gravitated away from that and we are now interested in asynchronous creation of CSSStyleSheet. This CL added Document.createCSSStyleSheet that returns a Promise<CSSStyleSheet>, while also removing the exposed CSSStyleSheet that was previously exposed. Note that because CSS parsing is still done on the main thread, this function is actually still blocking. The previously implemented CSSStyleSheet is changed to only produce empty CSSStyleSheets in this CL: crrev.com/c/1126898 Bug: 807560 Change-Id: I9f9d17ae04829ff399ae384f8b3a6d97a3b0613b Reviewed-on: https://chromium-review.googlesource.com/1126754 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Hayato Ito <hayato@chromium.org> Reviewed-by:
Takayoshi Kochi <kochi@chromium.org> Reviewed-by:
Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#575600}
-
Takayoshi Kochi authored
This was implemented in crbug.com/633007 but was never adopted by any standards, and could not get much attention from developers except for testing use cases. As this was dismissed from the standard, we have to pursue the testing use cases in other forms. Bug: 829713 Change-Id: I2b053a15e96d68ff5a8c632e65b7b2feefb15dab Reviewed-on: https://chromium-review.googlesource.com/999453Reviewed-by:
-
Markus Heintz authored
Bug: 850161 Change-Id: I1fdb08aa752c5297e59245065830955447e01cf1 Reviewed-on: https://chromium-review.googlesource.com/1127163 Commit-Queue: Markus Heintz <markusheintz@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#575598}
-
Vadym Doroshenko authored
This CL is implementation of overriding of prefilled values in username fields if the server believes that these values are placeholders. The life of server prediction for filling prefilled values is the following (it's called may_use_prefilled_placeholder in code): 1. The server sends it and it's propagated as part of FormStructure to FormParser (it's implemented before this CL). 2. It's parsed in password_field_prediction.cc to PasswordFieldPrediction 3. FormParser puts it to PasswordForm. 4. In password_form_fill_data.cc it's propagated to PasswordFormFillData 5. It's sent to the renderer over MOJO 6. PasswordAutofillAgent uses it to override prefilled values if any. The reason of putting processing may_use_prefilled_placeholder in FormParser not in NewPasswordFormManager is that NewPasswordFormManager should know nothing about form structure, it's FormParser responsibility to process it. Small deletion of dead code is done: parameter |set_selection| from FillUserNameAndPassword, since it's never set to true. Bug: 847793, 831123 Change-Id: Id86d0992428e520718a6ab6e9f50e8064444d030 Reviewed-on: https://chromium-review.googlesource.com/1124474 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Reviewed-by:
Vaclav Brozek <vabr@chromium.org> Cr-Commit-Position: refs/heads/master@{#575597}
-
Javier Fernandez authored
Leading white-spaces are indeed breaking opportunities that should prevent, if there are no other css properties forcing it, breaking text in the middle of a word when honoring the word-wrap/overflow-wrap CSS property. We are doing so if the leading white-space sequence is longer than 1 character, but when we have a single leading white-space, we are missing that breaking opportunity and we may lead to cases, like the one described in the bug. However, this breaking opportunity should be considered together with other provided by the word-break CSS property (eg, break-word or break-all). There is a discussion [1] in the CSS WG github about this issue, which provides an interoperability analysis of a few cases where a single leading white-space character may produce different results, depending on the browser and the combination of line-breaking properties. [1] https://github.com/w3c/csswg-drafts/issues/2907 Bug: 854624 Change-Id: I49ec8282e899a32990662c104b48cab04057b909 Reviewed-on: https://chromium-review.googlesource.com/1130515 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#575596}
-
Yuichiro Hanada authored
This CL introduces InputMethodSurface class for handling input method surface role. Also the version of remote_shell interface is bumped to 17. Bug: 845079 Test: Ran on DUT. Change-Id: I79d26a941deb621c5155e53ad6989414a6bd3614 Reviewed-on: https://chromium-review.googlesource.com/1131052 Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#575595}
-
Matt Falkenhagen authored
The file has many tests. Give it a long timeout. Bug: 863160 Change-Id: Idfad60c6e088b97bdc279c648037ecbf5d33861f Reviewed-on: https://chromium-review.googlesource.com/1139935Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#575594}
-
Kenichi Ishibashi authored
These are not recorded when S13nServiceWorker is enabled. Bug: 852673 Change-Id: I0dd94ec089e7a6e36b0cc9fbc2ee85078e622725 Reviewed-on: https://chromium-review.googlesource.com/1119738Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#575593}
-
Kenichi Ishibashi authored
When we load subresorces from the main thread and dedicated workers we use RenderViewImpl's RendererPreferences to check DNT header should be set or not. Since RenderViewImpl may not be available for service workers we need another way to pass RendererPreferences from browser to renderer. This CL adds a method to ContentBrowserClient to get RendererPreferences from chrome/ to content/, and piggybacks the preferences in EmbeddedWorkerStartParams to populate it from browser to renderer. Bug: 853085 Change-Id: Ibdd6bac46bbf0e27c02866f496482041e8789138 Reviewed-on: https://chromium-review.googlesource.com/1130967 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
-
Javier Fernandez authored
We should not extend selection looking for special elements if the delete operation has been triggered by a caret based selection. This change is based on a recent [1] resolution of the Editing TF, which acknowledges that behavior of single-cell tables must be the same that multi-cell tables and even if the last character is deleted, we should not delete the whole table structure. A different case would be when the user actively selects the whole content of a table; in this case, as we do in multi-cell tables, the structure of single-cell tables should be deleted together with the content. [1] https://github.com/w3c/editing/issues/163 Bug: 731320 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I8c3e4efcc63410bf30b4889a715d92e9dda8189b Reviewed-on: https://chromium-review.googlesource.com/1126255 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#575591}
-
Mark Cogan authored
This CL updates the tab grid transitions to cleanly match the presented tab views. The basic abstraction for this transition is the GridToTabTransitionView protocol which defines a set of 'cell' and 'tab' views, and methods to lay them out. The general idea is that a view conforming to this protocol can either be in 'cell' mode (where it exactly matches a tab grid cell), or in 'tab' mode (where it exactly matches an open tab). Most of the work is done by the GridTransitionCell subclass of GridCell, which positions and scales the "tab" and "cell" views it is supplied with so they animate smoothly. All of this positioning/scaling logic is internal to that class and nothing else depends on it. Providing the transition cell with the tab views is handled in the transition animator, mostly leveraging the content area layout guide. This doesn't require any direct integration with the tab view (that is, the BVC) beyond that layout guide. Approaches I abandoned: - letting -layoutSubviews position the tab/grid views. The problem with this approach (which is much cleaner from an API perspective) is that the timing of the layout passes is unpredictable, it it resulted in changes being made that weren't fully animated (for example, subviews would be scaled and positioned without animation, and then the superview would scale with an animation). - using layout constraints for GridTransitionCell's tab views. This is probably the correct thing to do long-term; mostly this was a decision made under time constraints, but since ultimately animating constraint changes depends on -layoutSubviews being called at the right times, I did have some concerns given the difficulties described above. It's unfortunate that grid_cell.mm is mixing constraint- and frame-based layout, but it is confined to that single file. Bug: 851460, 850507, 862343 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: If6d55f14aa05e705143547b61773fdb34796ad2d Reviewed-on: https://chromium-review.googlesource.com/1136647 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
-
Mark Cogan authored
Per the bug, add corner rounding and change the scale of the reduced motion animation. Note that this CL uses 26px corner radius for better visibility given how brief the animation is. Bug: 851871 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I9f2c3b02ce53abed3570f33a09017ee7a9273ed1 Reviewed-on: https://chromium-review.googlesource.com/1138618Reviewed-by:
edchin <edchin@chromium.org> Commit-Queue: Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#575589}
-
Mark Cogan authored
This CL fixes the problem of the tab grid (the root view controller) being briefly visible when the app launches. Note that this problem isn't simply a matter of the initial tab view controller (the BVC) being presented with an animation at launch; even if the presentation isn't animated, the tab grid is visible for several frames as the app launches. The fix in this CL is to (again) insert the launch image view on top of the tab grid during launch. This is done inside the TabGridCoordinator. If the launch view is present, the presentation of the tab view controller isn't animated. The launch view is removed the first time a presentation completes, and it is never added again. There are a few problems with this approach that should be resolved after M69 launches: - Futzing around with view hierarchies isn't something a coordinator should do. I'm doing it that way here because it at least keeps things well-contained. - Jamming the launch view in to spackle over UIKit glitches is getting kind of old. Bug: 826288 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I701b550f9eef16452a608b839c9a321b6b7a966a Reviewed-on: https://chromium-review.googlesource.com/1138329Reviewed-by:
-
Mikel Astiz authored
This reverts commit 1e3235b3. Reason for revert: suspect for breaking webkit_layout_tests on Mac, e.g. test offset-from-point-complex-scripts.html. Bug: 864405 Original change's description: > Add support for mid ligature positions > > Makes XPositionForOffset and CharacterIndexForPosition support > return results inside a ligature glyph (while still not breaking ZWJs) > by using a character-based TextBreakIterator inside glyphs. > > Bug: 473476 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel > Change-Id: I723cc8ba081958ff2d470d3e73ead6cbe327cf60 > Reviewed-on: https://chromium-review.googlesource.com/1085554 > Reviewed-by: Emil A Eklund <eae@chromium.org> > Reviewed-by: Koji Ishii <kojii@chromium.org> > Reviewed-by: Dominik Röttsches <drott@chromium.org> > Commit-Queue: Fernando Serboncini <fserb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#575496} TBR=eae@chromium.org,kojii@chromium.org,drott@chromium.org,fserb@chromium.org Change-Id: Id20c3aca9139d65e4187009e7ef7b45f87cceb5e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 473476 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Reviewed-on: https://chromium-review.googlesource.com/1140073Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#575587}
-
Ned Nguyen authored
Bug:863767 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ibe182c3bc7acaf9a0519da2eb365e443df460d68 TBR=perezju@chromium.org Change-Id: Ibe182c3bc7acaf9a0519da2eb365e443df460d68 Reviewed-on: https://chromium-review.googlesource.com/1138407Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#575586}
-
Sergei Datsenko authored
If feature flags has changed drivefs may need a restart before it's able to serve requests. In this case mounting will fail. Make browser handle this situation by retrying after some time. BUG=chromium:845390,chromium:845388 Change-Id: I0d4cdcf0e981b0966a23d91d3dc6fd30a32fb927 Reviewed-on: https://chromium-review.googlesource.com/1139943Reviewed-by:
Sam McNally <sammc@chromium.org> Commit-Queue: Sergei Datsenko <dats@chromium.org> Cr-Commit-Position: refs/heads/master@{#575585}
-
Alexey Khoroshilov authored
Bug: 849582 Change-Id: I6e75d9a62b4b58569c2c29b913c0a6a0cab0bf83 Reviewed-on: https://chromium-review.googlesource.com/1139057Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Alexey Khoroshilov <sense@yandex-team.ru> Cr-Commit-Position: refs/heads/master@{#575584}
-
Sergey Poromov authored
In order to ensure investigation of the issue when extensions are not yet loaded after 5 minutes (timeouted), double-check pending list. For the case if there are policy configured extensions that are installed, but not loaded, new metrics will be reported: Extensions.ForceInstalledTimedOutAndNotInstalledCount BUG=787970 TEST=Unit tests updated Change-Id: I2ade477fe96e9b32546c4ce819c4316ff31b17bd Reviewed-on: https://chromium-review.googlesource.com/1135246 Commit-Queue: Sergey Poromov <poromov@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
-
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: I533bb35d10dcf5a35ee0ab8abc1d855fed0df256 Reviewed-on: https://chromium-review.googlesource.com/1139905Reviewed-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@{#575582}
-
Alexey Baskakov authored
Modernize it. Add unit test. Bug: 860581 Change-Id: I136f85f234a843321b49976659f37aa2865ba318 Reviewed-on: https://chromium-review.googlesource.com/1139844 Commit-Queue: Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#575581}
-
Ioana Pandele authored
This CL: - Adds 24dp spacing in between the generated password text view and the explanation text view. - Changes the padding of the generation dialog's custom view layout to 24dp. - Changes the text line height to 20sp. - Changes the appearance of the generated password text. Bug: 835234 Change-Id: I4e9a683298674ab81e67fb08c39a9d5dcdd3e3b3 Reviewed-on: https://chromium-review.googlesource.com/1138327Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#575580}
-
Yutaka Hirano authored
With this CL, CORSURLLoader::fetch_cors_flag_ which represents the CORS flag in the spec will not be set if the request's mode is "no-cors". This CL also fixes how the origin header is attached. Bug: 736308 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I9cc510377ad97ec0ac99039e98b888e1eb91f2f6 Reviewed-on: https://chromium-review.googlesource.com/1139938Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#575579}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/9fb90f83997a..bf2a980d03db git log 9fb90f83997a..bf2a980d03db --date=short --no-merges --format='%ad %ae %s' 2018-07-17 skia-bookmaker@skia-swarming-bots.iam.gserviceaccount.com Update markdown files Created with: gclient setdep -r src/third_party/skia@bf2a980d03db 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=bungeman@chromium.org Change-Id: I8a791798941543b77cddb1db60fb00c7d54f43f8 Reviewed-on: https://chromium-review.googlesource.com/1139913Reviewed-by:
-
Ramin Halavati authored
Switch EnableEphemeralFlashPermission switch's default value to true. Bug: 850062 Change-Id: I42cc3adb918f9c0e95d5ad17f08577d6149b3999 Reviewed-on: https://chromium-review.googlesource.com/1138238 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#575577}
-
Mikel Astiz authored
This reverts commit 02a52f51. Reason for revert: suspect of causing test failures on multiple bots for test flexbox-with-overflow-auto-child-crash.html. Bug: 864402 Original change's description: > [layoutng] Use the correct layout algorithm to compute min/max sizes > > This also required adding a check in NGBlockNode::ComputeMinMaxSize > for whether we are inside of PerformLayout -- on Mac, we can > compute preferred sizes outside of layout; however, we can't do > actual layout in that case, so we have to fallback to legacy > min/max size in this case (c.f. RenderViewImpl::CheckPreferredSize()) > > Bug: 635619 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng > Change-Id: I0caf0c6c79264074ccaf9f45b83a420950dab715 > Reviewed-on: https://chromium-review.googlesource.com/1131562 > Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> > Reviewed-by: Morten Stenshorne <mstensho@chromium.org> > Cr-Commit-Position: refs/heads/master@{#575545} TBR=cbiesinger@chromium.org,ikilpatrick@chromium.org,mstensho@chromium.org Change-Id: I02d8cbfe883bafb2a3780ec46bd11b9e786678f4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 635619 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/1140033Reviewed-by:
-
Kent Tamura authored
We'd like to fix a confusing UI issue, and to know the impact of a possible fix. Bug: 637639 Change-Id: I7af67ac314f61723c7904cf0fee408ac2b60e774 Reviewed-on: https://chromium-review.googlesource.com/1139940 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#575575}
-
