- 23 Jul, 2018 14 commits
-
-
Rakina Zata Amni authored
This CL moves ReportFindInPageMatchCount and ReportFindInPageSelection from RenderFrameImpl to FindInPage. This is done in preparation of mojoifying FindInPage::Find. ReportFindInPage{MatchCount,Selection} sends FindReply frame host messages through IPC for calls to the Find method. After mojoification, these functions will instead call SetNumberOfMatches/SetActiveMatch on FindInPageClient. We are moving them now to make the CL for the mojoification smaller/simpler. Mojoifying doc: https://goo.gl/JenyGm Previous CLs: Introduce FindInPageClient with SetNumberOfMatches and SetActiveMatch crrev.com/c/1080568 Mojoify FindInPage::StopFinding crrev.com/c/1058731 (other CLs linked in the CL above) Bug: 819919 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I2841d2841a44d1473d4118215cd7dd0f238ca001 Reviewed-on: https://chromium-review.googlesource.com/1097237Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#577112}
-
Noel Gordon authored
Add helper to read the "full test case name". Any derived classes that have testing options (TabletMode, GuestMode, etc) can include those in the full test case name. Update FileManagerBrowertestBase to log the "full test case name" when starting a browser test. Bug: 836254 Change-Id: I9613a4682a6ae91fb03a842ce20924ceb21c1930 Reviewed-on: https://chromium-review.googlesource.com/1146412 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#577111}
-
Timothy Loh authored
This reverts commit 26399bca. Reason for revert: OmniboxViewViewsTest.SelectAllOnTabToFocus is Flaky Original change's description: > Match security chip visibility with focus ring > > Instantly hides or shows the IconLabelBubbleView separator when focus > rings are available to prevent showing the separator when a focus ring > overlaps it. > > Bug: chromium:865029 > Change-Id: I21a4c296c1da06b81dc91d66101d46e8ad52ad99 > Reviewed-on: https://chromium-review.googlesource.com/1142442 > Commit-Queue: Peter Boström <pbos@chromium.org> > Reviewed-by: Bret Sepulveda <bsep@chromium.org> > Cr-Commit-Position: refs/heads/master@{#576358} TBR=pbos@chromium.org,bsep@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 865029, 866230 Change-Id: I30372e90c1613b33690b43dd28fbe151abddddef Reviewed-on: https://chromium-review.googlesource.com/1146421Reviewed-by:
Timothy Loh <timloh@chromium.org> Commit-Queue: Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#577110}
-
Khushal authored
This reverts commit 13e510ef. Reason for revert: Causing crashes on the latest canary. I'll debug on Monday. Original change's description: > gpu: Hook up activity flags for glProgramBinary for OOPR. > > The activity flags are used to notify the browser if the GPU process > crashes during shader compilation which could indicate a corrupted disk > shader cache. Hook this up for the persistent shader caching on the > GrContext for OOPR. > > R=ericrk@chromium.org, piman@chromium.org > > Bug: 854416 > 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: I4ed69d41768856b649a500dd5b86777bf0023d26 > Reviewed-on: https://chromium-review.googlesource.com/1142367 > Reviewed-by: Antoine Labour <piman@chromium.org> > Commit-Queue: Khushal <khushalsagar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#576819} TBR=khushalsagar@chromium.org,piman@chromium.org,ericrk@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 854416 Change-Id: I51f5ff5b7427348b06159b7a8a3ec11161d9b6f3 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 Reviewed-on: https://chromium-review.googlesource.com/1146087Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#577109}
-
Timothy Loh authored
This reverts commit 5c4bc1ff. Reason for revert: CanvasRenderingContext2DTest.LowLatencyIsSingleBuffered failing I suppose this depended on https://chromium-review.googlesource.com/c/1144602/, which was reverted, so the test this CL adds is failing now. Original change's description: > Add a single buffered mode to CanvasResourceProvider > > This CL completes the initial implementation of Low Latency mode for 2d > canvases > > Bug: 788439 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel > Change-Id: I58fcd3fe4ab19fa10f2876f3da4f078fd4fbc2a9 > Reviewed-on: https://chromium-review.googlesource.com/1145235 > Commit-Queue: Justin Novosad <junov@chromium.org> > Reviewed-by: Fernando Serboncini <fserb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#576962} TBR=junov@chromium.org,fserb@chromium.org NOTRY=TRUE Bug: 788439,866211 Change-Id: I8e976b4cb6aca452f6d1891677e35e4411e2a5e4 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Reviewed-on: https://chromium-review.googlesource.com/1146460 Commit-Queue: Timothy Loh <timloh@chromium.org> Reviewed-by:
Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#577108}
-
Yutaka Hirano authored
Bug: 736308 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I86bccc93b2e2050326d59c26a03d05a51ed1ae81 Reviewed-on: https://chromium-review.googlesource.com/1144807 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Chong Zhang <chongz@chromium.org> Cr-Commit-Position: refs/heads/master@{#577107}
-
Rakina Zata Amni authored
FindInPageClient is a per-frame client for FindInPage. FindRequestManager has a map of frame -> FindInPageClient. FindInPageClient manages per-frame number of matches, and also updates the global number of matches and the current active match rect and ordinal. In this CL, we are changing ActivateNearestFindResult to call methods on FindInPageClient instead of calling a callback. SetNumberOfMatches is called to update the corresponding frame's number of find-in-page matches and also update the total number of matches in a tab. SetActiveMatch updates the tab's active match rect and ordinal. When we mojoify FindInPage::Find, we'll use FindInPageClient to receive the find replies and remove FindRequestManager::OnFindReply. Mojoifying doc: https://goo.gl/JenyGm Previous CLs: Mojoify FindInPage::StopFinding crrev.com/c/1058731 (other CLs linked in the CL above) Bug: 819919 Change-Id: I25a6d81037655801db1b1337f335073f11aa7862 Reviewed-on: https://chromium-review.googlesource.com/1080568 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#577106}
-
Timothy Loh authored
This reverts commit c2bc780a. Reason for revert: Lots of breakages on Debug builders # Fatal error in ../../v8/src/api.cc, line 5960 # Check failed: expected == value ((nil) vs. 0x11b5bca8d0e8). # # # #FailureMessage Object: 0x7fff42dfe070#0 0x7fd6fdc375fd base::debug::StackTrace::StackTrace() #1 0x7fd6fd9443cc base::debug::StackTrace::StackTrace() #2 0x7fd6e76e76f7 gin::(anonymous namespace)::PrintStackTrace() #3 0x7fd6dad0b918 V8_Fatal() #4 0x7fd6f9eecfcc v8::String::VerifyExternalStringResourceBase() #5 0x7fd6e2a5a310 blink::ToBlinkString<>() #6 0x7fd6e501a9f5 blink::V8StringResource<>::ToString<>() #7 0x7fd6e501416c blink::V8StringResource<>::operator WTF::AtomicString() #8 0x7fd6e69322d1 blink::ElementV8Internal::removeAttributeMethod() #9 0x7fd6e6931faa blink::V8Element::removeAttributeMethodCallback() #10 0x7fd6f9fa5444 v8::internal::FunctionCallbackArguments::Call() #11 0x7fd6f9fa3870 v8::internal::(anonymous namespace)::HandleApiCallHelper<>() #12 0x7fd6f9fa1ba8 v8::internal::Builtin_Impl_HandleApiCall() #13 0x7fd6f9fa15e1 v8::internal::Builtin_HandleApiCall() #14 0x7fd6fac565f5 <unknown> Received signal 4 ILL_ILLOPN 7fd6dad10b62 #0 0x7fd6fdc375fd base::debug::StackTrace::StackTrace() #1 0x7fd6fd9443cc base::debug::StackTrace::StackTrace() #2 0x7fd6fdc37054 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7fd6df1c60c0 <unknown> #4 0x7fd6dad10b62 v8::base::OS::Abort() #5 0x7fd6dad0b925 V8_Fatal() #6 0x7fd6f9eecfcc v8::String::VerifyExternalStringResourceBase() #7 0x7fd6e2a5a310 blink::ToBlinkString<>() #8 0x7fd6e501a9f5 blink::V8StringResource<>::ToString<>() #9 0x7fd6e501416c blink::V8StringResource<>::operator WTF::AtomicString() #10 0x7fd6e69322d1 blink::ElementV8Internal::removeAttributeMethod() #11 0x7fd6e6931faa blink::V8Element::removeAttributeMethodCallback() #12 0x7fd6f9fa5444 v8::internal::FunctionCallbackArguments::Call() #13 0x7fd6f9fa3870 v8::internal::(anonymous namespace)::HandleApiCallHelper<>() #14 0x7fd6f9fa1ba8 v8::internal::Builtin_Impl_HandleApiCall() #15 0x7fd6f9fa15e1 v8::internal::Builtin_HandleApiCall() #16 0x7fd6fac565f5 <unknown> Original change's description: > Update V8 to version 7.0.1. > > Summary of changes available at: > https://chromium.googlesource.com/v8/v8/+log/d7b61abe..8766d3dd > > 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: Id0a466229f294e8afa3e887d9814926b592815b7 > Reviewed-on: https://chromium-review.googlesource.com/1145698 > Reviewed-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@{#576998} TBR=hablich@chromium.org,v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com,v8-waterfall-sheriff@grotations.appspotmail.com NOTRY=TRUE Change-Id: I86ecc3dba8ab82f9e2968b3905033539f9363098 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 Reviewed-on: https://chromium-review.googlesource.com/1146420 Commit-Queue: Timothy Loh <timloh@chromium.org> Reviewed-by:
Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#577105}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=amineer@chromium.org Change-Id: I674947b92fc11e1aac2b4855d0a87fe1c8f7c9a2 Reviewed-on: https://chromium-review.googlesource.com/1146212Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#577104}
-
Xiaocheng Hu authored
This patch removes a header inclusion for better build performance, and clearer code dependency. Bug: 866120 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I8d3bb813807bbae08350f1b649043752a1198d42 Reviewed-on: https://chromium-review.googlesource.com/1145694 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#577103}
-
Stefan Zager authored
This is an abstraction to facilitate moving the bulk of platform/scroll into core. WebScrollbarTheme provides a Mac-only API which is called into from content, and affects the styling of all scrollbars. After this patch, all of the other scrollbar and scrollbar theme code can move out of platform. BUG=823365 R=skobes@chromium.org,chrishtr@chromium.org TBR=dgozman@chromium.org Change-Id: I888e08676b5343156ae391c44b2084e90023de0f Reviewed-on: https://chromium-review.googlesource.com/1141116 Commit-Queue: Stefan Zager <szager@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#577102}
-
Darren Shen authored
In a previous patch, we removed KeyboardLayoutManager's dependency on KeyboardController's SetContainerType. This means that the friend declaration in KeyboardController is no longer needed. TBR=blakeo@chromium.org Bug: 845780 Change-Id: I56ea22d989dcefc3bc70d4ca054678fd52c5bef7 Reviewed-on: https://chromium-review.googlesource.com/1146139Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#577101}
-
Timothy Loh authored
This CL adds a vector icon for use in notifications for Linux packages. Using a vector icon allows this to get blue/red colours automatically to match the notification title color. Bug: 822464 Change-Id: Ie21f437b8c65aefb8d5be4732e864f826445d361 Reviewed-on: https://chromium-review.googlesource.com/1143046Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#577100}
-
Darren Shen authored
There are two ways for the keyboard window bounds to change. Either through KeyboardController or through JavaScript / the IME extension. Notably, we always receive a JavaScript bound change when initializing the keyboard UI. To handle bounds changes from JavaScript, we use a LayoutManager to intercept those changes and forward them to KeyboardController. In production, the LayoutManager is installed by ash::Shell. In unit tests however, we do not always have this setup because the test may not be able to depend on ash. Unit tests that load the keyboard will simulate the initial JavaScript bound change, but because there's no layout manager, KeyboardController does not receive the update and gets into a bad state. The current workaround is to manually add a LayoutManager to the root window in tests that need it. This is not ideal, as the correctness of KeyboardController is silently dependent on the construction of a LayoutManager [*]. To fix this, we observe bounds changes to the keyboard window in KeyboardController. Then, KeyboardController will no longer need the LayoutManager to notify bounds changes; it can observe them directly. [*] We didn't have this problem before because we could install the layout manager on the keyboard container, which was part of the KeyboardController. Since we got rid of the keyboard container, we can only install the layout manager on an ash container, which is external to KeyboardController. Bug: 845780 Change-Id: I053778f04ab3ccf4d13fcd79d05832f9238b21b5 Reviewed-on: https://chromium-review.googlesource.com/1133607Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#577099}
-
- 22 Jul, 2018 13 commits
-
-
Darren Shen authored
We shouldn't show the emoji menu item in the render view context menu for "number", "tel" and "other" (dates, time, checkboxes etc.) input types. We deliberately implement this as a blacklist (don't show for these input types) instead of a whitelist (only show for these input types), since not being able to enter emoji when you should be able to is much more frustrating than having an extraneous emoji item. Note that this permits emoji on "password" fields, but apparently that could be a thing. Bug: 865199 Change-Id: I7b2b977f435cee0c4f98c357187b45d90a08ecfc Reviewed-on: https://chromium-review.googlesource.com/1142851Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#577098}
-
Kai Koehne authored
The check for cpu.family() == 15 will also trigger for newer ThreadRipper CPU's, resulting in a DCHECK on debug builds and potentially suboptimal behavior in release builds. To fix this, the check would have to take the extFamily() and maybe model() into account, but I couldn't find the correct values for the AMD K2 CPU's anywhere. Anyhow, it is unclear whether newer Windows versions are still affected by the original problem. The commit that introduced the original check - https://codereview.chromium.org/4092 - is more than 9 years old. There are hints that the underlying issue got fixed in Windows XP SP2 and/or Windows 7. Hence this patch just removes the check. Bug: 863855 Change-Id: I26d6e282ec6116ec40fbf86e750367d15dc31604 Reviewed-on: https://chromium-review.googlesource.com/1138241 Commit-Queue: Yuri Wiitala <miu@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#577097}
-
Javier Fernandez authored
This reverts commit 6ea2a2e7. Reason for revert: <INSERT REASONING HERE> Original change's description: > [css-text] A leading white-space should break before handling overflow > > 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} TBR=jfernandez@igalia.com,kojii@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 854624 Change-Id: I9ee4cd370dd92b74f9fdc4f42d16638253dd2dee Reviewed-on: https://chromium-review.googlesource.com/1146360Reviewed-by:
Javier Fernandez <jfernandez@igalia.com> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#577096}
-
Christopher Cameron authored
Previous patch to disable compositor recycling only disabled for BridgedNativeWidget. Now disable for everything. TBR=ericrk Bug: 863817863817863817863817 Change-Id: I09fed3b84e7df23d540c4a4db528f43efa8bac15 Reviewed-on: https://chromium-review.googlesource.com/1146325Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#577095}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/dfe1fe40796e..df795638b9bd git log dfe1fe40796e..df795638b9bd --date=short --no-merges --format='%ad %ae %s' 2018-07-22 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update SKP version Created with: gclient setdep -r src/third_party/skia@df795638b9bd 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: Ie0323b78036acfc3efde3f15c5d439074ac9c66f Reviewed-on: https://chromium-review.googlesource.com/1146085Reviewed-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@{#577094}
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: I189d6028291aa0744e7a55d0f159bc9e8d1fec8c Reviewed-on: https://chromium-review.googlesource.com/1146292 Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#577093}
-
Wez authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: I3b5c09e02dcce92f990db6211319d4b0cbc11b9e Reviewed-on: https://chromium-review.googlesource.com/1146287Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#577092}
-
Jochen Eisinger authored
Bug: 865157 Change-Id: I6d04148640812e4a2de80866fee1545bd2ef1868 Reviewed-on: https://chromium-review.googlesource.com/1141874 Commit-Queue: Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#577091}
-
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: I624481c18c89d49535d585ce1a5448e92f545924 Reviewed-on: https://chromium-review.googlesource.com/1146282Reviewed-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@{#577090}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/881fe53d1fae..0c3ad73948e4 git log 881fe53d1fae..0c3ad73948e4 --date=short --no-merges --format='%ad %ae %s' 2018-07-21 buildbot@webrtc.org Roll chromium_revision 86c90e34..5e7b1029 (576937:577041) 2018-07-20 benwright@webrtc.org Adds SSLCertificateVerifier to the Java API. 2018-07-20 mbonadei@webrtc.org Enable clang::find_bad_constructs for sdk/android (part 1/2). 2018-07-20 buildbot@webrtc.org Roll chromium_revision 7002a7d3..86c90e34 (576827:576937) 2018-07-20 aleloi@webrtc.org Reset level estimator when analog gain changes. 2018-07-20 mbonadei@webrtc.org Enable clang::find_bad_constructs for audio_coding (part 1/2). 2018-07-20 mbonadei@webrtc.org Enable clang::find_bad_constructs for api/video/test. 2018-07-20 mbonadei@webrtc.org Enable clang::find_bad_constructs for rtc_tools (part 1/2). 2018-07-20 buildbot@webrtc.org Roll chromium_revision bc3d35fc..7002a7d3 (576524:576827) 2018-07-20 mbonadei@webrtc.org Enable clang::find_bad_constructs for remote_bitrate_estimator. 2018-07-19 qingsi@google.com Remove MetricsObserverInterface. 2018-07-19 mbonadei@webrtc.org Enabling clang::find_bad_constructs for desktop_capture. 2018-07-19 braveyao@webrtc.org [Window capture] filter out sibling windows with same title. 2018-07-19 mbonadei@webrtc.org Reland "Removing unneeded dependency." 2018-07-19 buildbot@webrtc.org Roll chromium_revision ecaca1be..bc3d35fc (576410:576524) 2018-07-19 oprypin@webrtc.org Follow "Migrate the Android Support Lib to android_deps" from Chromium 2018-07-19 yvesg@webrtc.org Expose audio codec factories in libwebrtc. 2018-07-19 aleloi@webrtc.org Fuzzer finds fixedpoint failure. 2018-07-19 mbonadei@webrtc.org Enabling clang::find_bad_constructs for libjingle_peerconnection_api. 2018-07-19 stefan@webrtc.org Rename PayloadRouter to RtpVideoSender. 2018-07-19 mbonadei@webrtc.org Enabling clang::find_bad_constructs in modules/BUILD.gn. 2018-07-19 buildbot@webrtc.org Roll chromium_revision 6374eaa6..ecaca1be (576310:576410) 2018-07-19 mbonadei@webrtc.org Clean up unneeded includes in common_video/BUILD.gn. 2018-07-19 mbonadei@webrtc.org Clean up unneeded includes in common_audio/BUILD.gn. 2018-07-19 mbonadei@webrtc.org Clean up unneeded includes in audio_device/BUILD.gn. 2018-07-19 buildbot@webrtc.org Roll chromium_revision 9e818a5a..6374eaa6 (576197:576310) 2018-07-19 hta@webrtc.org Add UMA metric for ICE candidate addition outcome 2018-07-19 jeroendb@webrtc.org Added explicit EOR to sctp messages and coalesce messages on the receiving side. 2018-07-18 benwright@webrtc.org Adds flag to enable AES_GCM from the Java API. 2018-07-18 buildbot@webrtc.org Roll chromium_revision 7e9fce12..9e818a5a (576093:576197) 2018-07-18 benwright@webrtc.org Added API to Objective-C PeerConnectionFactoryOptions to enable GCM Ciphers. 2018-07-18 buildbot@webrtc.org Roll chromium_revision 9159e523..7e9fce12 (575979:576093) 2018-07-18 mbonadei@webrtc.org Cleanup unneeded includes in audio_coding/BUILD.gn. 2018-07-18 sakal@webrtc.org Allow calling SoftwareVideoDecoderFactory#createDecoder(String). 2018-07-18 orphis@webrtc.org Implement changing degradation preference with setParameters() 2018-07-18 mbonadei@webrtc.org Revert "Removing unneeded dependency." 2018-07-18 stefan@webrtc.org Properly clean up RtpVideoSender. 2018-07-18 terelius@webrtc.org Limit BWE reductions before first measured throughput. 2018-07-18 mbonadei@webrtc.org Enabling clang::find_bad_constructs for modules/pacing. 2018-07-18 mbonadei@webrtc.org Removing unneeded dependency. 2018-07-18 mbonadei@webrtc.org Enabling clang::find_bad_constructs for common_video. 2018-07-18 mbonadei@webrtc.org Removing clang:find_bad_constructs from logging (part 1). 2018-07-18 mbonadei@webrtc.org Revert "Remove linux_internal_compile_lite from CQ." 2018-07-18 mbonadei@webrtc.org Adding oprypin to infra/config/OWNERS. 2018-07-18 buildbot@webrtc.org Roll chromium_revision 9ec8cfdb..9159e523 (575625:575979) 2018-07-18 ilnik@webrtc.org Reland "Enable simulcast screenshare by default" Created with: gclient setdep -r src/third_party/webrtc@0c3ad73948e4 The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng BUG=chromium:None,chromium:None,chromium:None,chromium:865193,chromium:None,chromium:864883,chromium:None,chromium:None,chromium:713701,chromium:None,chromium:713701,chromium:None,chromium:None,chromium:None,chromium:None,chromium:690537 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I761335ea240c6da495ddad33ad073d42bd446453 Reviewed-on: https://chromium-review.googlesource.com/1146084Reviewed-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@{#577089}
-
Justin Cohen authored
Bug: 865119 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ic2a6fdb250075d14306eb4f581b8443f05632d8f Reviewed-on: https://chromium-review.googlesource.com/1145851 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#577088}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: Ibeccd2133bf66ff72525f2c37e4bb7eb472f07b2 Reviewed-on: https://chromium-review.googlesource.com/1146205Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#577087}
-
Justin Cohen authored
Previously the NTP 'scroll up' animation and the omnibox 'focus' animation happened concurrently when tapping on the NTP fakebox. Instead, chain these animations, so the NTP fakebox 'scroll up' animations completes and then focuses the real omnibox. Also changes how the 'scroll up' animation works to use a CADisplayLink, so each tick of the scroll updates the fakebox shape and hint label size. See: https://drive.google.com/open?id=11dbkXTl0V0n5WODLiBYezpdkH-eUvxKO Bug: 865408, 865822 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I85d8d193178602a434e4f0007513c38be69e9fec Reviewed-on: https://chromium-review.googlesource.com/1142946Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#577086}
-
- 21 Jul, 2018 13 commits
-
-
Daniel Cheng authored
If the extent is static, there's no need to store the size in a field: the size is already contained in the type. Bug: 866043 Change-Id: I5456e54055d76eb88f20bd8da257be3e2a5941d6 Reviewed-on: https://chromium-review.googlesource.com/1145959 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#577085}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/cc22d4d2fb02..dfe1fe40796e git log cc22d4d2fb02..dfe1fe40796e --date=short --no-merges --format='%ad %ae %s' 2018-07-21 herb@google.com Convert bitmap to use runs instead of blobs Created with: gclient setdep -r src/third_party/skia@dfe1fe40796e 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: I2004e6b389fa08d635ab0a439627212839923776 Reviewed-on: https://chromium-review.googlesource.com/1146083Reviewed-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@{#577084}
-
François Beaufort authored
This CL makes sure native video controls don't show a Picture-in-Picture button when video src is a MediaStream as backend is not implemented yet. Bug: 806249 Change-Id: I04171b2ba73e3689334809c6419bcc8ff598196f Reviewed-on: https://chromium-review.googlesource.com/1145076Reviewed-by:
apacible <apacible@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#577083}
-
Sunny Sachanandani authored
This reverts commit 6beef1e6. Reason for revert: Causes test failures e.g. https://chromium-swarm.appspot.com/task?id=3ed41ac799e41d10&refresh=10&show_raw=1 Original change's description: > cc: Throttle incoming begin frames in scheduler > > Unlike PostTask from IO thread to compositor thread in Chrome IPC, mojo > polls for messages on the compositor thread which means it can dequeue a > large number of begin frame messages after the compositor thread has > been busy for some time. All but the last begin frame cancels the > previous begin frame, and is essentially a nop, but it still ticks > animations. When a page has a large number of animations each begin > frame can take a long time and push out other tasks such as tile manager > callbacks stalling the pipeline. > > Throttling the begin frames in viz doesn't fully solve the problem > because we have to allow at least two begin frames in flight for > pipelining, and so the client can still process two begin frames back to > back. > > Throttling in AsyncLTFS causes issues with LTFS lifetime and ordering > with respect to other messages. > > Saving incoming begin frame in scheduler and posting a task works and > ensures that only one begin frame is outstanding at any time. > > R=danakj > BUG=782002 > > Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel > Change-Id: I247a87ad7475d33f878a215ce87056d20482f88c > Reviewed-on: https://chromium-review.googlesource.com/1130082 > Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> > Reviewed-by: danakj <danakj@chromium.org> > Cr-Commit-Position: refs/heads/master@{#577046} TBR=danakj@chromium.org,sunnyps@chromium.org Change-Id: I0ce088ef781f93cc4b392c347f443771f84249a6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 782002 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Reviewed-on: https://chromium-review.googlesource.com/1146082Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#577082}
-
Christopher Cameron authored
In SwapBuffersInternal, change the order of calls from - wait on old fence - create new fence - flush To - flush - create new fence - wait on old fence If the crashes are a result of the GL context being in a bad state, then the glFlush may crash instead of the GLFence::Create call. Note that this glFlush is and always was redundant, because GLFenceARB already has an explicit call to glFlush. Also allow the function to early-out if there is no current CGL context. Also ensure that recycled compositors have the same ui::ContextFactory as was requested. Bug: 863817 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: I2d2b71ff38c032669663607015e7f0afd374e230 Reviewed-on: https://chromium-review.googlesource.com/1144056 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#577081}
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ddcfa34d6ad4..9e8a0b2b37d9 git log ddcfa34d6ad4..9e8a0b2b37d9 --date=short --no-merges --format='%ad %ae %s' 2018-07-21 benjhayden@chromium.org ReportQuery supports the new ReportTemplate system. Created with: gclient setdep -r src/third_party/catapult@9e8a0b2b37d9 The AutoRoll server is located here: https://catapult-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=sullivan@chromium.org Change-Id: I989a06a9c3ec7cee02b8514474dbdb24560de0d3 Reviewed-on: https://chromium-review.googlesource.com/1146081Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#577080}
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: I6b9916ebb4d47b969e95a730e9007920f6eb3bc9 Reviewed-on: https://chromium-review.googlesource.com/1146079 Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#577079}
-
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: I2fefa4274a7db459146253ce90bd665926e425ea Reviewed-on: https://chromium-review.googlesource.com/1146078Reviewed-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@{#577078}
-
P.Y. Laligand authored
Updates the Fuchsia sysroot location. TBR=dpranke Change-Id: I2e4b01fe6d7ed114faa9d00679aaf206d58a3124 Reviewed-on: https://chromium-review.googlesource.com/1146031 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#577077}
-
Koji Ishii authored
Following bot results are included. 8106 8107 8113 8119 8130 8137 8141 8151 8154 8155 8165 8172 8177 8178 8180 6 lines were removed and 5 lines were deflaked by consecutive results since 8119. TBR=eae@chromium.org, mstensho@chromium.org NOTRY=true Bug: 591099 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I36a06760bfb22c1ff3c0402d86072790f6737ca0 Reviewed-on: https://chromium-review.googlesource.com/1143437 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#577076}
-
Min Qin authored
InProgressDownloadManager could get created before DownloadManagerImpl ctor. And DownloadManagerService will own the InProgressDownloadManager in that case. This CL allows DownloadManagerImpl to retrieve the pre-created InProgressDownloadManager from DownloadManagerService BUG=695115 Change-Id: Ie2d553894e623116a5e09ae54ec4b8672b180c7f Reviewed-on: https://chromium-review.googlesource.com/1135986 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#577075}
-
Tarun Bansal authored
Bug: 866212 Change-Id: Ia74a20e7061590fafadf69ac13ac595f1c6c4f8e TBR: dougarnett@chromium.org Reviewed-on: https://chromium-review.googlesource.com/1146060 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#577074}
-
Christopher Cameron authored
This should be based off of the ui::Layer heirarchy, not the NSView heirarchy. Bug: 860344 Change-Id: I307a1d681a21846886bb6118a3e3acf97c2b268e Reviewed-on: https://chromium-review.googlesource.com/1144215 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#577073}
-