- 28 Nov, 2017 40 commits
-
-
Miguel Casas authored
This CL teaches WebMVideoClient to parse the |codec_private| field, if present, to figure out the VP9 Profile if any. This is a necessary step to support VP9.2 10b on Vaapi. TEST=crosvideo.appspot.com/?codec=vp9.2&loop=true and newly added unittests. Bug: 778093, 592074 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Ic62519b32818fe409d15f54b6ddb9798deea88da Reviewed-on: https://chromium-review.googlesource.com/786211 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Sergey Volk <servolk@chromium.org> Cr-Commit-Position: refs/heads/master@{#519519}
-
Dave Tapuska authored
Unbuffered dispatch mode is very analogous to the Android version. It will send touchmove/mousemoves immediately while the pointer is down. If the target is a HTML Canvas it is queried if it is in unbuffered dispatch mode and if it is the mode is requested from the input queue. BUG=788234 Change-Id: Ib92e9f52c9b32e52c6b90dd2c002adaedf361f96 Reviewed-on: https://chromium-review.googlesource.com/789550 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Justin Novosad <junov@chromium.org> Reviewed-by:
Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#519518}
-
Primiano Tucci authored
Passing these callbacks from the client process code means that MDM begins owning the callback. However, these callbacks *must* be run before destruction. While this is not a problem with MDM per-se as MDM is a leaky singleton, MDM ocassionally passes ownership of this callback to a thread loop. On destruction of the thread loop with the callback posted, the callback could be destroyed without being run which can cause problems. To solve this, instead of passing the callback into a situation where it could be destroyed, we instead store the callback inside the client process itself. As the client is also a leaky singleton, the destructor of these callbacks will no longer be run so we do not have the above problem. Bug: 788658 Change-Id: I9dd65fe7748e0afaedd1bf5a3d25ac9cadfe9853 Reviewed-on: https://chromium-review.googlesource.com/790591Reviewed-by:
Primiano Tucci <primiano@chromium.org> Commit-Queue: Primiano Tucci <primiano@chromium.org> Cr-Commit-Position: refs/heads/master@{#519517}
-
Kyle Horimoto authored
This CL introduces the GattServicesWorkaround class with an implementation and test double. The class is initialized as part of the asynchronous shutdown flow and is invoked by BleConnectionManager when GATT services are unavailable. Bug: 784968, 672263 Change-Id: If81085bf9f8c7ac7f6715f93f9c3c07a8dbc13e2 Reviewed-on: https://chromium-review.googlesource.com/777983Reviewed-by:
Jeremy Klein <jlklein@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#519516}
-
Lei Zhang authored
In various components/[a-c]* directories. Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ic42b2176db06d2adbf35d815932c54aed6d3c255 Reviewed-on: https://chromium-review.googlesource.com/776020Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#519515}
-
rbpotter authored
Add individual closure compiler targets for data elements needed by new UI. Bug: 773928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: If4f877da51d174e06b09ac4618f7ac1c56096cae Reviewed-on: https://chromium-review.googlesource.com/792014Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#519514}
-
Stefan Zager authored
The text diffs are due to the new layer tree structure. The image diffs are only on Win10, and they appear to be shading differences due to antialiasing. Most likely, this is caused by floating point numerical differences when the printing code applies a zoom factor to the page. BUG=711468 R=pdr@chromium.org,skobes@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_root_layer_scrolls Change-Id: I0d33a98a98bdf5203f26f97ab7787c162619af1c Reviewed-on: https://chromium-review.googlesource.com/792332Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#519513}
-
Jose Dapena Paz authored
Remove all the ATK implementation in BrowserAccessibilityAuraLinux, and relay on the single implementation available in AXPlatformNodeAuraLinux. This way we stop duplicating ATK implementation, and focus on a single backend for the whole platform accessibility. Some changes were needed in AXPlatformNodeAuraLinux to support the requirements in BrowserAccessibility: * Delegate AccessibilityTreeAuraLinux AddProperties on AXPlatformNodeAuraLinux::AddAccessibilityTreeProperties. * Regenerate if needed the backing AXPlatformNodeAuraLinux ATK objects when OnDataChanged is called in BrowserAccessibilityAuraLinux. Bug: 784583 Change-Id: I9538f09e5018a252e56c446270f8197742faa0d0 Reviewed-on: https://chromium-review.googlesource.com/788395 Commit-Queue: José Dapena Paz <jose.dapena@lge.com> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#519512}
-
Gustav Sennton authored
See crbug.com/786608 for details - in this CL we CHECK the fields that could possibly be causing a bad mojo message. BUG=786608 Change-Id: I4b467653a24623da9a748306be6034e8d8a2d0a4 Reviewed-on: https://chromium-review.googlesource.com/790298Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Gustav Sennton <gsennton@chromium.org> Cr-Commit-Position: refs/heads/master@{#519511}
-
Changwan Ryu authored
Add some logging messages that are guarded by DEBUG = false. With this, you can leave useful debugging messages without having to resolve merge conflicts every time. BUG= Change-Id: Ic9b47bcd250e59021041bfe0ecfebb87a0a5182d Reviewed-on: https://chromium-review.googlesource.com/792345Reviewed-by:
Tao Bai <michaelbai@chromium.org> Commit-Queue: Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#519510}
-
Lei Tian authored
Reland "Use TabPersistentStoreObserver.onMetadataSavedAsynchronously to background the Browser Actions tab creation service" This relands commit 64565fd7. Original change's description: > Use TabPersistentStoreObserver.onMetadataSavedAsynchronously to background the Browser Actions tab creation service > > Change the logic to background the Browser Actions tab creation service > based on TabPersistentStoreObserver.onMetadataSavedAsynchronously. The > callback indicates that tab model lists are backuped so the saved tabs > can be restored succesfully. > > Also for the notification when a new tab has not been created (tabId is > not available), the Intent to bind the notification will be a VIEW > intent. This notification is necessary to make the service foreground. > > Bug: 766349 > Change-Id: I73d49e2a1e26410b2dd6e51a07f35e9965b9a38a > Reviewed-on: https://chromium-review.googlesource.com/769852 > Reviewed-by: Ted Choc <tedchoc@chromium.org> > Commit-Queue: Lei Tian <ltian@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517492} Bug: 766349 Change-Id: Icb35c3b0e3ed2186e48c7f0e77ceb6a07bc1f39f Reviewed-on: https://chromium-review.googlesource.com/791392Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Lei Tian <ltian@chromium.org> Cr-Commit-Position: refs/heads/master@{#519509}
-
Scott Little authored
The constants for recognizing Weblite URLs are now controlled by field trial params, and the logic is handled in native code for easier unit testing. Bug: 717592 Change-Id: I4a853db2555d82ede32a95efd00ed3a224dc87ab Reviewed-on: https://chromium-review.googlesource.com/786173Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Reviewed-by:
Ben Greenstein <bengr@chromium.org> Commit-Queue: Scott Little <sclittle@chromium.org> Cr-Commit-Position: refs/heads/master@{#519508}
-
Allen Vicencio authored
Add Mount and Unmount. CQ-DEPEND=CL:782708 Bug: chromium:757625 Change-Id: Idbc9ccc80da7872317f3a0bd05b72447e09de1d0 Reviewed-on: https://chromium-review.googlesource.com/745304 Commit-Queue: Allen Vicencio <allenvic@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Reviewed-by:
Lutz Justen <ljusten@chromium.org> Reviewed-by:
Roman Sorokin <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#519507}
-
angle-deps-roller@chromium.org authored
https://chromium.googlesource.com/angle/angle.git/+log/ebee5b3b7de5..0b684ce3c9f5 $ git log ebee5b3b7..0b684ce3c --date=short --no-merges --format='%ad %ae %s' 2017-11-23 jmadill Vulkan: Move RenderPass init into a helper function. 2017-11-23 jmadill ContextImpl: Make flush/finish take a gl::Context. Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=jmadill@chromium.org Change-Id: Ieea792672e8b9baa6149e48260fb81011c63c85c Reviewed-on: https://chromium-review.googlesource.com/791861Reviewed-by:
angle-deps-roller . <angle-deps-roller@chromium.org> Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#519506}
-
Wez authored
This is a reland of 7df6fead, which was speculatively reverted as possible cause of crbug.com/788192, since the CL originally landed only after that regression. Original change's description: > Migrate call-sites away from un-managed PlatformHandle[Vector]s. > > As the first step to merging ScopedPlatformHandle into PlatformHandle > to have a single, always-managed container for platform handles, we: > > - Replace ScopedPlatformHandleVectorPtr and PlatformHandleVector > with vector<ScopedPlatformHandle>. > - Replace PlatformHandle with ScopedPlatformHandle in some core APIs. > - Use const& to pass handles to APIs without passing ownership, for > both individual platform handles, and vectors. > > Bug: 753541 > Change-Id: Id965dcf3770ef11bf36f78277fa7199ea779599e > Reviewed-on: https://chromium-review.googlesource.com/742309 > Reviewed-by: Ricky Liang <jcliang@chromium.org> > Reviewed-by: Ken Rockot <rockot@chromium.org> > Reviewed-by: Dominick Ng <dominickn@chromium.org> > Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> > Commit-Queue: Wez <wez@chromium.org> > Cr-Commit-Position: refs/heads/master@{#518343} Bug: 753541 TBR: lhchavez, jcliang, dominickn, rockot Change-Id: I9d50f06052b2118aec8872ca149504fbed245f1a Reviewed-on: https://chromium-review.googlesource.com/792255Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#519505}
-
Christopher Cameron authored
Bug: Change-Id: Ifec62565e096220b53149fd77e9bc96e46caa7c1 Reviewed-on: https://chromium-review.googlesource.com/792390Reviewed-by:
Fredrik Hubinette <hubbe@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#519504}
-
Ian Vollick authored
Previously, there were many spots in the UI unittests where we checked that a set of UI elements (and only that set of UI elements) was visible. This had regressed, however, and in the interim, elements had been added that were not accounted for in the test expectations. In this CL, I have switched back to exclusive visibility checks, and have updated the appropriate expectations. I have also introduced the notion of an owner elements. This both permits unit tests to refer to unnamed sub-elements meaningfully and allows for better debug output (the hierarchy dumps are much more meaningful). This also permitted including these unnamed sub-elements in the stacking unit test. I have also moved the remaining stacking unit tests into the UI unittests. I have also updated the backplane click test to simulate the response to the click so we can check that the visuals update as we expect. Bug: 782395 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I8f4f0fb92df18dc6b8d7a8e086768d4a97136898 Reviewed-on: https://chromium-review.googlesource.com/789440 Commit-Queue: Ian Vollick <vollick@chromium.org> Reviewed-by:
Christopher Grant <cjgrant@chromium.org> Reviewed-by:
Yash Malik <ymalik@chromium.org> Cr-Commit-Position: refs/heads/master@{#519503}
-
pdfium-deps-roller@chromium.org authored
https://pdfium.googlesource.com/pdfium.git/+log/9b93815edae6..e82af1a845c1 $ git log 9b93815ed..e82af1a84 --date=short --no-merges --format='%ad %ae %s' 2017-11-27 npm Make ConvertBuffer_* void 2017-11-27 dsinclair Convert CFX_GifContext::GetFrameNum to size_t Created with: roll-dep src/third_party/pdfium The AutoRoll server is located here: https://pdfium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: I8783e80687aefb651c887ec2fde59b37c7f1ba80 Reviewed-on: https://chromium-review.googlesource.com/792291 Reviewed-by: <pdfium-deps-roller@chromium.org> Commit-Queue: <pdfium-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#519502}
-
Michael Thiessen authored
We were posting display rAF for magic window when there was no reason to, which was making comparing window rAF and display rAF performance difficult. This CL fixes that, and adds a test to make sure display rAF is equivalent to window rAF in terms of scheduling. This exposes the same race in getFrameData_oneframeupdate.html that was found in WebVrTabTest#testPoseDataUnfocusedTab, namely that the pose can start off being null, racily. The previous behavior of posting the vrDisplay rAF was hiding this. Bug: 734747, 734208, 787196 Change-Id: Ib6b657b1966359683b3c7aca16be26be9c3c54dd Reviewed-on: https://chromium-review.googlesource.com/788240 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#519501}
-
Trent Apted authored
This probably "regressed" in r503368, which fixed a use case for accelerator handling. But that meant that accelerator handling happened before Textfield::OnKeyEvent() handling, resulting in a stray edit command because Textfield::AcceleratorPressed() doesn't clear it. However, Textfield::AcceleratorPressed() doesn't do the right thing on Mac anyway. On Mac, these always dispatch via the responder chain and the `Edit` menu in the main menu bar. This ensures they obey custom key mappings that a user may have set up in System Preferences via string matching on the specific menu items. Bug: 773565 Change-Id: Ic09db94866b6bd37791517505b24211c6c1105c4 Reviewed-on: https://chromium-review.googlesource.com/788632 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#519500}
-
bsheedy authored
Fixes the issue of CCT/WAA NFC tests getting stuck in the DOFF flow. This was somehow caused by the webpage listening for vrdisplayactivate, but not actually presenting with it. Also adds a sleep at the end of the test to prevent a possible race condition with VrCore's 2 second NFC debounce timeout. Bug: 787878 Change-Id: Ic5f16258cfa94ce3fac63781c1e225b8b2749f4e Reviewed-on: https://chromium-review.googlesource.com/791938 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#519499}
-
Maria Khomenko authored
Records the time since last main frame navigation when a renderer OOM is detected. On Android record only foreground OOMs. BUG=736892 Change-Id: I71424844a7bfc9528a6ec865249b046e65275e07 Reviewed-on: https://chromium-review.googlesource.com/769234 Commit-Queue: Maria Khomenko <mariakhomenko@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#519498}
-
John Z Wu authored
//ios/web_view has unittests for autofill which use TestWebState. Bug: Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: If6abe86f6bfb7bb3ab718aa1d5cc4e8fb180812a Reviewed-on: https://chromium-review.googlesource.com/791816Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: John Wu <jzw@chromium.org> Cr-Commit-Position: refs/heads/master@{#519497}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 87a4dbb1. Build: https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/6423 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md TBR=rbyers No-Export: true Change-Id: I1fe90dda18eda2775a5eac729db7bb35165c2b39 Reviewed-on: https://chromium-review.googlesource.com/792070 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#519496}
-
Lei Zhang authored
In various [d-z]* directories. Change-Id: Ia434e9935a4c03a710f58627fd470de309f91f3e Reviewed-on: https://chromium-review.googlesource.com/786532Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#519495}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a6639fb9..5784f65c 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I5ef4fc23a864000d3b54702ede806495d8287340 Reviewed-on: https://chromium-review.googlesource.com/792211Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#519494}
-
Lei Zhang authored
gfx: :Point(gfx_rect.x(), gfx_rect.y()) is the same as gfx_rect.origin(). Change-Id: I092ce75a52a9dc73b303396398963091af8b265d Reviewed-on: https://chromium-review.googlesource.com/784394Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#519493}
-
Yusuf Ozuysal authored
This is a follow up to the first CL that enables TrustedWebActivities. - Adds an OriginVerifier on Activity level and falls back to showing the toolbar if verification fails. - Moves the WebApk side offline dialog handling in the splashscreen controller to WebappSplashScreenController, plumbing through the app package name and using the tab's Activity to show. This way both TrustedWebActivity and WebAPK's could use it. BUG= 782905 Change-Id: I9314ac846cdf237ecc1a3d0104e18d967285017e Reviewed-on: https://chromium-review.googlesource.com/773482 Commit-Queue: Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#519492}
-
wutao authored
Currently Launcher dismiss animation is using SetBounds, which will call SetBoundsFromAnimation on each OnProgress. This will generate additional overhead with a whole commit every frame. This cl converts it to use ThreadedTransformTransition, which will let compositor optimize and accelerate the animation. Eve with DCHECK build, improved average smoothness from 84% to 99%. Bug: 788928 Test: Change-Id: I10a3fcb8c2895d71bf262b30c72b9f67fd0634ea Reviewed-on: https://chromium-review.googlesource.com/792001Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#519491}
-
Karan Bhatia authored
NPAPI plugin support has been removed from chrome and the "plugins" extension manifest key is effectively deprecated. This CL deprecates the internal plugin permission, which an extension gets on non ChromeOS platforms, when it specifes plugins in its manifest. This is safe since r518752 should ensure that we are not using the plugins specified in the manifest. Also the concept of "implies_full_access" for API permissions is removed. Behavior changes this introduces: - On non ChromeOS platforms, extensions which specify plugins in their manifest would no longer get the IDS_EXTENSION_PROMPT_WARNING_FULL_ACCESS permission message. - Since the plugins permisison is deprecated, it is no longer considered while determining if an extension's priveleges have increased. BUG=732590 Change-Id: Ic9c8c1c27815cafff18c792da887aec9066eb655 Reviewed-on: https://chromium-review.googlesource.com/784557 Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#519490}
-
Lindsay Pasricha authored
Tests were dependent upon this accessibility ID, but no longer are, so now removing the ID. Bug: 695077 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I603bf02322717dc0ef210b04208689ad4d375ced Reviewed-on: https://chromium-review.googlesource.com/791892Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> Cr-Commit-Position: refs/heads/master@{#519489}
-
gogerald authored
Test video: https://drive.google.com/file/d/1oUUkOqj5EJU9XiXUp9fz1FxC6S6knNqW/view?usp=sharing Bug: 785309 Change-Id: I14f7ae6b879bea7f805d7a9de8320231447e9a81 Reviewed-on: https://chromium-review.googlesource.com/788250 Commit-Queue: Ganggui Tang <gogerald@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#519488}
-
Fabio Tirelo authored
Registry keys removed or changed by the cleaner will be shown to the user on the Settings page card and need to be provided by the cleaner via the Mojo IPC. Those keys are only used for visualization (no validation will be done by Chrome) and we don't intend to add any sophisticated visualization support (such as expandable trees); because of that, we decided to go with the simplest approach and only transmit lists of strings instead of more structured data. This CL only propagates registry keys to the places they may be used, so most files in this CL are simply adding a new parameter to functions. A follow-up CL will actually use the new parameter in UI code. Bug: 776538 Change-Id: Ifd9faf79eea070d17452356c45ae37482bf77864 Reviewed-on: https://chromium-review.googlesource.com/780287 Commit-Queue: Fabio Tirelo <ftirelo@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Jialiu Lin <jialiul@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#519487}
-
Xianzhu Wang authored
This avoids crash on unexpected null TotalPropertyTreeStateForContents() in https://chromium-review.googlesource.com/c/chromium/src/+/786130 for SPv175/non-RootLayerScrolling. This is separated from that CL which is a pure SPv175 refactor. Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I5ad8db400838f4e9a5a5f87847e62858c6460759 Reviewed-on: https://chromium-review.googlesource.com/791935 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#519486}
-
François Degros authored
This way, if one of the CHECK_PAGE_IN_CORE fails, we get a more accurate message with a useful line number, and not just a line number within the (now removed) local function CheckPageInCore. Also fixed the way mincore is used. According to mincore's documentation: int mincore(void *addr, size_t length, unsigned char *vec); The vec argument must point to an array containing at least (length+PAGE_SIZE-1) / PAGE_SIZE bytes. On return, the least significant bit of each byte will be set if the corresponding page is currently resident in memory, and be clear otherwise. The settings of the other bits in each byte are undefined; these bits are reserved for possible later use. Change-Id: I47f11e896a21944033314a84c6775d3d2ff70a24 Bug: 788240 Reviewed-on: https://chromium-review.googlesource.com/788473 Commit-Queue: François Degros <fdegros@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#519485}
-
Jerome Jiang authored
https://chromium.googlesource.com/webm/libvpx.git/+log/ea14a1a965c5..cbe62b9c2d2b $ git log ea14a1a96..cbe62b9c2 --date=short --no-merges --format='%ad %ae %s' 2017-11-21 marpan vp9-svc: Fix to the layer buffer settings. 2017-11-20 vtsyrklevich [CFI] Remove function pointer casts 2017-11-20 jianj vp8 simulcast: fix compile warnings. 2017-11-17 marpan vp9-svc: Enbale scale partition reference frames. 2017-11-17 jianj vp9 svc: fix a few compile warnings. 2017-11-17 kylesiefring Optimize AVX2 get16x16var and get32x16var functions 2017-11-16 paulwilkins Disable allow_partition_search_skip for speed 2. 2017-11-15 paulwilkins Code cleanup. 2017-11-15 paulwilkins Remove decay_accumulator clause from alt ref breakout. 2017-11-15 paulwilkins Add clause to alt ref group breakout. Created with: roll-dep src/third_party/libvpx/source/libvpx R=johannkoenig@google.com Bug: Change-Id: Ie6724cbc3e03f47bf6151e60029bf954d958018d Reviewed-on: https://chromium-review.googlesource.com/792112Reviewed-by:
Johann Koenig <johannkoenig@google.com> Commit-Queue: Jerome Jiang <jianj@google.com> Cr-Commit-Position: refs/heads/master@{#519484}
-
Jana Iyengar authored
This reverts commit ba355778. Reason for revert: This change causes QUIC to be marked as broken if it happens ip change happens during a handshake, which may be causing QUIC usage to go down. Original change's description: > Default enables option to close QUIC sessions on an IP address change, > when QUIC connection migration is not enabled. > > Bug: 544156 > Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester > Change-Id: I6440c4833e798b61d2d83dcef2f1bf24869719be > Reviewed-on: https://chromium-review.googlesource.com/655767 > Reviewed-by: Paul Jensen <pauljensen@chromium.org> > Reviewed-by: Ryan Hamilton <rch@chromium.org> > Commit-Queue: Jana Iyengar <jri@chromium.org> > Cr-Commit-Position: refs/heads/master@{#503577} TBR=pauljensen@chromium.org,rch@chromium.org,jri@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 544156 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I619b6201d33cd4f97bb8be8f1674e319fa9196fe Reviewed-on: https://chromium-review.googlesource.com/759356 Commit-Queue: Jana Iyengar <jri@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Reviewed-by:
Jana Iyengar <jri@chromium.org> Cr-Commit-Position: refs/heads/master@{#519483}
-
John Z Wu authored
The autorelease pool released the mock objects so that nothing was actually being tested. Bug: Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I90c575bd82e6662d264c377b7d30a23cfc100e90 Reviewed-on: https://chromium-review.googlesource.com/792006Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: John Wu <jzw@chromium.org> Cr-Commit-Position: refs/heads/master@{#519482}
-
Hans Wennborg authored
TBR=hans Change-Id: Ib55a96609180af705988496d879cf525804e78bc Reviewed-on: https://chromium-review.googlesource.com/792336Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#519481}
-
Mrunal Kapade authored
Following up from https://codereview.chromium.org/2905733003/ Replace with DLOG(INFO) instead. BUG=638849 Change-Id: I773fba7a2b0c09d5e55e645096eb3c3cad698324 Reviewed-on: https://chromium-review.googlesource.com/678056Reviewed-by:
Fredrik Söderquist <fs@opera.com> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Mrunal Kapade <mrunal.kapade@intel.com> Cr-Commit-Position: refs/heads/master@{#519480}
-