- 16 Oct, 2018 40 commits
-
-
Alexander Alekseev authored
This Cl prepares for bug 596743 and has fixes to clear for https://chromium-review.googlesource.com/c/chromium/src/+/1269235 landing. Bug: 892757 Change-Id: I9858ec633158310c805430f1f070b5cff730f94f Reviewed-on: https://chromium-review.googlesource.com/c/1282462 Commit-Queue: Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#600149}
-
Brandon Wylie authored
Bug: 888712 Change-Id: I6f89d30906700b7b5f4fe283a749a09c5a6e59ce Reviewed-on: https://chromium-review.googlesource.com/c/1250061 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Robert Kaplow (sloooow) <rkaplow@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#600148}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/88afab4ff0f0..b273e0cd217d git log 88afab4ff0f0..b273e0cd217d --date=short --no-merges --format='%ad %ae %s' 2018-10-16 lwsong@google.com Add aggregate graphs to visualization tool. 2018-10-16 perezju@chromium.org [telemetry] Fix typo in WebSocketException 2018-10-16 perezju@chromium.org [soundwave] Remove old comment Created with: gclient setdep -r src/third_party/catapult@b273e0cd217d The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:876681 TBR=sullivan@chromium.org Change-Id: I5fdc43203e194660ce62571123e9f8003626dfc1 Reviewed-on: https://chromium-review.googlesource.com/c/1284569Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600147}
-
rbpotter authored
crbug.com/804047 has been fixed, and the DCHECK referenced in the Print Preview JS no longer occurs. Remove the async(..., 1) workaround. Bug: None Change-Id: I0a8f38a697965e912265092d33ef7a2d0e58f85f Reviewed-on: https://chromium-review.googlesource.com/c/1281912Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#600146}
-
Nate Fischer authored
No change to default behavior, because this logic is behind a flag. This blocks billing threats in WebView, and adds some tests for this functionality. This involves: * Add necessary resources to WebView's whitelist * Test Loud and Quiet interstitials * Test we use the correct threat type integer in onSafeBrowsingHit * Test that the Feature is disabled on trunk * Add hardcoded WebUI URL for billing interstitial (also for Chrome) R=changwan@chromium.org, vakh@chromium.org Feature enabled via commandline flag. This is necessary to stay consistent with Chrome. Bug: 887186 Test: run_webview_instrumentation_test_apk --gtest_filter=SafeBrowsingTest#*Billing* Test: Manual - load chrome://safe-browsing/match?type=billing with Binary-Size: Increase is due to added WebView strings for the new interstitials. Change-Id: I695c39ffdd79ef5e771027953bfffc327fc6864b Reviewed-on: https://chromium-review.googlesource.com/c/1270476Reviewed-by:Carlos IL <carlosil@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#600145}
-
Vlad Tsyrklevich authored
Bug: 894423 Change-Id: I10e809b1b745f2c9d0fdcbf6bd1f958d1aec0103 Reviewed-on: https://chromium-review.googlesource.com/c/1283934Reviewed-by:
Max Moroz <mmoroz@chromium.org> Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Cr-Commit-Position: refs/heads/master@{#600144}
-
Scott Violet authored
This will be used to ensure events are properly updated based on whether the delegate handles the event or not. BUG=891489 TEST=none Change-Id: I94fd4f8b781dbf725b7c2c6ac0d540986c24c24f Reviewed-on: https://chromium-review.googlesource.com/c/1262404 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#600143}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/1927dfafabc0..9b1d67982f26 git log 1927dfafabc0..9b1d67982f26 --date=short --no-merges --format='%ad %ae %s' 2018-10-16 mbonadei@webrtc.org Remove 'iOS32 Sim Debug (iOS 9.0)' from client.webrtc. 2018-10-16 niklas.enbom@webrtc.org Revert "Remove the HighPassFilter interface" 2018-10-16 peah@webrtc.org Avoids creating empty call_order file when no call order data is written 2018-10-16 danilchap@webrtc.org Calculate max payload size for an rtp packet to fit full video frame 2018-10-16 srte@webrtc.org Don't send max allocation probe unless allocation changed. 2018-10-16 terelius@webrtc.org Update proto for new event log format. 2018-10-16 nisse@webrtc.org Delete wrappers for snprintf and vsnprintf 2018-10-16 magjed@webrtc.org Use color aligning in video quality analysis tool 2018-10-16 peah@webrtc.org AEC3: Changes to initial behavior and handling of saturated echo 2018-10-16 mbonadei@webrtc.org Export symbols needed by the Chromium component build (part 3). 2018-10-16 srte@webrtc.org Using more specific dependencies in rtc_base. 2018-10-16 danilchap@webrtc.org Always verify packet wasn't resend recently before resending it. 2018-10-16 brandtr@webrtc.org Remove |hw_encoder| and |hw_decoder| from VideoCodecTestFixture::Config. 2018-10-16 nisse@webrtc.org Delete unused code in rtc_base/stringutils.* 2018-10-16 artit@webrtc.org Add generate_ios_coverage_command.py script 2018-10-16 srte@webrtc.org Removing unnecessary dependencies on socket.h. 2018-10-16 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0cecb6ce..f8cad916 (599821:599923) 2018-10-16 saza@webrtc.org Remove AECM comfort noise setting from API 2018-10-16 saza@webrtc.org Remove the HighPassFilter interface 2018-10-16 peterhanspers@webrtc.org Adding support for logging severity LS_NONE. 2018-10-16 nisse@webrtc.org Implement test class LoopbackMediaTransport 2018-10-16 asapersson@webrtc.org Add test that verifies that VideoEncoderConfig max_framerate is reported to source. 2018-10-16 srte@webrtc.org Removes Clock instance from RoundRobinPacketQueue. Created with: gclient setdep -r src/third_party/webrtc@9b1d67982f26 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng BUG=chromium:894434,chromium:895435,chromium:895431,chromium:None,chromium:844647,chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ic49f27d148d1b629d7599b62fd91ba2a28e30935 Reviewed-on: https://chromium-review.googlesource.com/c/1284010Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600142}
-
Hans Wennborg authored
New Clang versions started taking enumerations into account for the -Wshadow warning: ../../third_party/blink/renderer/platform/bindings/dom_wrapper_world.h:62:5: warning: declaration shadows a variable in namespace 'blink' [-Wshadow] kEmbedderWorldIdLimit = IsolatedWorldId::kEmbedderWorldIdLimit, ^ ../../third_party/blink/public/platform/web_isolated_world_ids.h:12:3: note: previous declaration is here kEmbedderWorldIdLimit = (1 << 29), ^ ../../third_party/blink/renderer/platform/bindings/dom_wrapper_world.h:63:5: warning: declaration shadows a variable in namespace 'blink' [-Wshadow] kIsolatedWorldIdLimit = IsolatedWorldId::kIsolatedWorldIdLimit, ^ ../../third_party/blink/public/platform/web_isolated_world_ids.h:16:3: note: previous declaration is here kIsolatedWorldIdLimit, ^ Bug: 895475 Change-Id: Idb37a14a6d7ca92b1e6bfa1d2fa3f42ffe64fe38 Reviewed-on: https://chromium-review.googlesource.com/c/1283024 Commit-Queue: Hans Wennborg <hans@chromium.org> Reviewed-by:Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#600141}
-
Jacob Dufault authored
Bug: 895995 Change-Id: Ibf2bc2ced1f502004b0ceac3830a2773ddac7ab9 Reviewed-on: https://chromium-review.googlesource.com/c/1284397Reviewed-by:
Quan Nguyen <qnnguyen@chromium.org> Commit-Queue: Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#600140}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/b708a096f473..0a3c5082ad50 git log b708a096f473..0a3c5082ad50 --date=short --no-merges --format='%ad %ae %s' 2018-10-16 chrome-bot@chromium.org Update config settings by config-updater. 2018-10-16 dgarrett@google.com chromeos_config: Remove nocturne / grunt firmwarebranch. Created with: gclient setdep -r src/third_party/chromite@0a3c5082ad50 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=chrome-os-gardeners@chromium.org Change-Id: Ibf36c6e9ad43dcb93e16fc91f6421e4a1c69ce86 Reviewed-on: https://chromium-review.googlesource.com/c/1284011Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600139}
-
David Bertoni authored
Add the "is_lazy," "is_for_service_workers," and "url" properties for event listeners. Bug: 891788 Change-Id: I8cabde8c8a8cf5935b448f1ec64aec25070f660e Reviewed-on: https://chromium-review.googlesource.com/c/1279197Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#600138}
-
Becky Zhou authored
On pre-N versions, the layout parameters can be ignored if we don't declare a root the inflated view. Updating the layout parameters only after view is attached to window. Bug: 895229 Change-Id: I671b83bbf6e72b9cbabb84e80636d68ba45c5dad Reviewed-on: https://chromium-review.googlesource.com/c/1282105 Commit-Queue: Becky Zhou <huayinz@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#600137}
-
Joel Einbinder authored
This prevents the user from accidentally hiding the frame view completely and being unable to figure out how to get it back. Bug: 895548 Change-Id: I39f503faa680bc136b14e6e521a1528ab594feff Reviewed-on: https://chromium-review.googlesource.com/c/1281873Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#600136}
-
Mustafa Emre Acer authored
This CL removes meacer@ and adds carlosil@ as an owner. Change-Id: Ic4ebf7b9b639ba7e23512cc80a73f29fd5f23b00 Reviewed-on: https://chromium-review.googlesource.com/c/1281241Reviewed-by:
Carlos IL <carlosil@chromium.org> Reviewed-by:
Vaclav Brozek <vabr@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#600135}
-
Antonio Gomes authored
This is a follow up of mmenke's request in [1]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/1281643/3#37 BUG=879783 Change-Id: If7267a4be836a1e8adfca5f7377fa57b53ebcd49 Reviewed-on: https://chromium-review.googlesource.com/c/1284449 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#600134}
-
Antonio Gomes authored
In [1], DataReductionProxyConfigServiceClient [2] switched from using URLFetcher to SimpleURLLoader for making URL requests. During the discussion phase with tbansal and cduvall, it was mentioned that the URLRequestContext specialization used by DataReductionProxyConfigServiceClient was originally needed to obey two criterias: (i) Use of SPDY and QUIC protocols is explicitly disabled; (ii) Use of any proxies is also disabled. Today, (i) isn't needed and (ii) can be obtained with a specific load flag: net::LOAD_BYPASS_PROXY. Hence, the URLRequestContext specialization (namely BasicHTTPURLRequestContextGetter) became unneeded, since (ii) can be easily respected with the default network context. This CL removes the left over BasicHTTPURLRequestContextGetter and associated code. [1] https://crrev.com/c/1274405 [2] components/data_reduction_proxy/core/browser/data_reduction_proxy_config_service_client.cc Bug=879784 Change-Id: Ib46fecbbe03c57f0fc9375cb8986da62d77bb525 Reviewed-on: https://chromium-review.googlesource.com/c/1284169Reviewed-by:
rajendrant <rajendrant@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#600133}
-
Jao-ke Chin-Lee authored
BUG=790343,864817 Change-Id: Ia6bbae90334828022d5ec994d5ab82427c1cb66d Reviewed-on: https://chromium-review.googlesource.com/c/1284769 Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org> Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Cr-Commit-Position: refs/heads/master@{#600132}
-
Javier Ernesto Flores Robles authored
This CL enables presentation in iPads as a popover instead of above the keyboard. This follows the UX design for Manual Fallback. - Makes sure the accessory bar for iPad is always added when Manual Fallback is Enabled. - The responsibility of not showing the accessory bar when other UI is presenting the keyboard is now fully own by the input accessory bar view controller. Bug: 845472 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: Ife13cc44b4912084ccb10376ee9c53039dc00548 Reviewed-on: https://chromium-review.googlesource.com/c/1256793 Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#600131}
-
Jeremy Roman authored
Bug: 670615 Change-Id: I2a7592581cc251b9f1a21171416ea3492932e218 Reviewed-on: https://chromium-review.googlesource.com/c/1281047Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#600130}
-
wutao authored
This is UI side code to handle buttons in assistant notification. Bug: b/117295934 Test: manual. Change-Id: I61144f418ba7af127c09892707ba442e8c5f5e65 Reviewed-on: https://chromium-review.googlesource.com/c/1274826 Commit-Queue: Tao Wu <wutao@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#600129}
-
Leo Liu authored
https://docs.google.com/document/d/1dzjfTfiTf_wVq_cwH85i2VQWDjKWt3ZsiqokZg21jjw/edit?usp=sharing Bug: b/117274233 Change-Id: I9ac16364a62cb8f55925dc8d5d04fdc5ce425ae9 Reviewed-on: https://chromium-review.googlesource.com/c/1277844Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Leo Liu <luciferleo@google.com> Cr-Commit-Position: refs/heads/master@{#600128}
-
Chris Blume authored
This CL adds support for Vulkan on windows but disables it in builds. This makes it easy to enable and test. BUG=850724 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: I8396b2f59133df5d72d1086cf22e154dba0bb15e Reviewed-on: https://chromium-review.googlesource.com/c/1270098 Commit-Queue: Chris Blume <cblume@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#600127}
-
Ella Ge authored
We used to have the touch adjustment range as 32dip in diameter (16dip in radius) for Android. After the zoom-for-dsf change, the pointerevent width & height became in physical pixel. It makes the actually range in dip much smaller on Android. This CL changes the adjustment range to be 32 CSS pixel, and apply the zoom_factor before compare with the pointerevent width&height. On Android, there is no ctrl +/- page zoom, so CSS pixel is dip. There is no change in behavior. On Desktop (aura), the adjustment upperbound is affected as it wasn't consider zooming before but now it does. Therefore, the bound will be affected by zoom_factor. On aura, there wasn't an upper bound for adjustment range before the unified touch adjustment change, which means the adjustment range is always the pointerevent width & height (physical pixel not changed). When we zoom in, the upper bound is increased, but the adjustment range will follow the finger size. So I think it's ok to make the bound changing with zooming as well on aura. Bug: 894961 Change-Id: I466d6b187359f13c82c62860086cb9eeef8cb2a5 Reviewed-on: https://chromium-review.googlesource.com/c/1279204 Commit-Queue: Ella Ge <eirage@chromium.org> Reviewed-by:
Rick Byers <rbyers@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#600126}
-
Shahbaz Youssefi authored
4c984bc7 requires angle to call a script in build/util/, but this directory is in src/ in chromium, and ./ in angle. Similar to how angle_root was defined to point to the right directory in each project, src_root is added to point to src/ or ./ depending on the project as well. This is necessary for angle to be able to roll its dependencies forward. Bug: angleproject:2892 Change-Id: I691d378c76bb238071a59db2298206eba55278bb Reviewed-on: https://chromium-review.googlesource.com/c/1283830Reviewed-by:
Geoff Lang <geofflang@chromium.org> Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org> Cr-Commit-Position: refs/heads/master@{#600125}
-
Peter Boström authored
Makes ToolbarActionView::DoShowContextMenu use GetAnchorBoundsInScreen which insets into the view to match the visible inkdrop hover effects. Bug: chromium:800372 Change-Id: Ibe2bfe93547bae75590c87214e2c1ed0b73aa37b Reviewed-on: https://chromium-review.googlesource.com/c/1281919Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#600124}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c3f52fd0306b..baa4e9b9a71c Created with: gclient setdep -r src-internal@baa4e9b9a71c The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I1304fe2a9b18c769175ae4f601d2aab92c2aa168 Reviewed-on: https://chromium-review.googlesource.com/c/1284429Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600123}
-
Meilin Wang authored
This metric should be the number of queries fired per each entry point, e.g. keyboard, OKG, launcher button, longpress applist. This includes the first query fired immediately after each entry point and follow up queries before window close. Test: local compile and manually test. Bug: b:117517666 Change-Id: I77c906ab95598a1e819f261462c50372c3aa07ea Reviewed-on: https://chromium-review.googlesource.com/c/1278149 Commit-Queue: Meilin Wang <meilinw@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#600122}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/bb3f58dbcb71..c3da36973048 git log bb3f58dbcb71..c3da36973048 --date=short --no-merges --format='%ad %ae %s' 2018-10-16 thestig@chromium.org Use unique_ptr in CFX_FolderFontInfo::ScanFile(). Created with: gclient setdep -r src/third_party/pdfium@c3da36973048 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: I9aa38e275f26822a58ce7c52fffb6526f94455d6 Reviewed-on: https://chromium-review.googlesource.com/c/1283515Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600121}
-
Michael Giuffrida authored
Hides Play Store in Demo Mode by default, because it doesn't show the right view yet. To test Play Store in Demo Mode after this CL, use the flag: --show-play-in-demo-mode Bug: 885370 Change-Id: I7119a208742caf3fd2884ac73176a9bbc19a2bde Reviewed-on: https://chromium-review.googlesource.com/c/1277841Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#600120}
-
Evan Stade authored
Use of TransientWindowClient and ActivationClient allow the same implementation to work in both classic and Mash. Bug: 640365 Change-Id: I10324dce04bb014c09d04f45c0be6e691017a648 Reviewed-on: https://chromium-review.googlesource.com/c/1271403Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#600119}
-
Michael Spang authored
Change-Id: I42a856d35b0fcee1b6340cebd766a3149d0d85db Reviewed-on: https://chromium-review.googlesource.com/c/1283475Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#600118}
-
Tarun Bansal authored
In Network Quality Estimator (NQE), remove the logic to compute increase in RTT since this is not being used anymore. Change-Id: Icf1785cf5a11152c529ac40da7da43110dce382e Bug: 895878 Reviewed-on: https://chromium-review.googlesource.com/c/1279946 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#600117}
-
Wez authored
In https://chromium-review.googlesource.com/c/chromium/src/+/754130 we switched to populating the is-repeat flag of ui::KeyEvent solely based on the flags in the underlying native event, if present. In the case of a key event triggering a pop-up window to appear, this caused the first auto-repeat of that event to be dispatched without the repeat flag set. To address this we restore the "fallback" path to manually determine whether an event should be flagged as a repeat, in the case of where a native event does not itself have the repeat flag set. Bug: 895266 Change-Id: Ia224e38768d67bf0dc74d60d7e5ed7b6b6663d80 Reviewed-on: https://chromium-review.googlesource.com/c/1281874Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#600116}
-
Andres Calderon Jaramillo authored
This CL changes JpegImageDecoder so that it doesn't advertise that it can support smaller decode sizes if the original size cannot fit a whole number of MCUs in both dimensions. This is done to prevent artifacts from showing up when downscaling certain images. dark line at the bottom. Test: opened the JPEG attached to the bug and verified that there is no Bug: 890745 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I884edcefc4bbd0612e621109c24aedc09cad3452 Reviewed-on: https://chromium-review.googlesource.com/c/1274845Reviewed-by:
Leon Scroggins <scroggo@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#600115}
-
Collin Baker authored
This is to reflect a change in the design doc. Bug: 887991 Change-Id: I8dbc058549ffd6bc9fbaf9d0d20d0d8d6ce30158 Reviewed-on: https://chromium-review.googlesource.com/c/1283938Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#600114}
-
Clark DuVall authored
Bug: 872343 Change-Id: Icb7aef94a64039b45f2284fc9ff9fe2dba33296e Reviewed-on: https://chromium-review.googlesource.com/c/1284062Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#600113}
-
rbpotter authored
Sometimes when the user is not signed in on debug builds, only ~5 destinations show up in the "Print destinations" list. Fix this by firing iron-resize when all destinations are done loading. Bug: None Change-Id: Id406b8aaaeccffd3a6419ea30a3396fc6ca7d157 Reviewed-on: https://chromium-review.googlesource.com/c/1282034Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#600112}
-
Xianzhu Wang authored
Android truncates long logs in __android_log_write. This is useful to avoid too verbose logs and save cpu/memory, but we do need some complete verbose logs for debugging. Now if DCHECK_IS_ON(), split long logs by new lines and call __android_log_write for each line to avoid the truncation. Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ib19c718a8f1d2fe1f2e155c38e1106174b38ae02 Reviewed-on: https://chromium-review.googlesource.com/c/1281883 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#600111}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/ab45d6915434..b407163ef346 git log ab45d6915434..b407163ef346 --date=short --no-merges --format='%ad %ae %s' 2018-10-16 stevenperron@google.com Checks for variable pointers (#1976) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@b407163ef346 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: Id4af123bcdb7f3bba922473ce27837100ebbbf56 Reviewed-on: https://chromium-review.googlesource.com/c/1284013Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#600110}
-