- 21 Oct, 2019 24 commits
-
-
Hsin-Yu Chao authored
We want to track the selected codec of all bluetooth HFP connections. Ideally we want the codec negotiation result to be mSBC, of value 2, which is by far the best quality codec. But there are cases it falls back to CVSD, of value 1. We want to track this value in order to know how frequent the failure happens. Patch in CRAS that send this value to UMA CL:1864253 Bug: 971568 Change-Id: Idf53fead80c7e4e055b85c00dd23cb322b1f9282 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865049 Commit-Queue: Hsinyu Chao <hychao@chromium.org> Auto-Submit: Hsinyu Chao <hychao@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#707716}
-
Chih-Yu Huang authored
In CL:1824303, we changed the flow of using V4L2 output buffers. At that CL, we forgot to enqueue V4L2 output buffers after we copy the content to bitstream buffers and free them. This CL fixes this issue by calling Enqueue() after that. BUG=chromium:1015257 TEST=tast run $(DUT) video.EncodeAccelPerfH264360PI420 on elm Change-Id: Iaa80779982c0c234ed9100095c9bb4b5b954288a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871150Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#707715}
-
Jason Lin authored
The visual design follows this spec [1]. [1]: https://bugs.chromium.org/p/chromium/issues/attachment?aid=352503&signed_aid=cMK94eiGY6JTFz05FJtiKw==&inline=1 Bug: 929571 Test: browser_tests --gtest_filter='CrostiniInstallerBrowserTest.*'; Manual testing Change-Id: I756872f7fb232b89ba9f85b49ecc1c907e4e1fce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833194 Commit-Queue: Jason Lin <lxj@google.com> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#707714}
-
Kenichi Ishibashi authored
The previous CL (crrev.com/c/1851624) seemed to make some tests flaky. I'm not sure the exact reason. This CL attempts to fix flakiness by not using default parameters. Bug: N/A Change-Id: Ia6fae23881704e4eb41e33ebe3e22e89872d7f87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866093 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#707713}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: If4b8f6d456c9f3a19292d104cc31665e7d88e6c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869827Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#707712}
-
Yoshifumi Inoue authored
This patch makes |NGCaretPosition| to utilize |NGInlineCursor| as part of migration to |NGFragmentItem|. Note: To reduce size of patch, following patches will utilize |NGInlineCursor| into caret rect, visible line etc. to replace |NGPaintFragment| usage to |NGInlineCursor|. Change-Id: I0d543204c0acba7b1ac215afed43b34295276d49 Bug: 982194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866101 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#707711}
-
Peter Kasting authored
Bug: 82078 Change-Id: I69c553e9746328e41880f8f51b5ec990303819a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866262 Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#707710}
-
Alice Boxhall authored
Also simplify the model, and fix an issue where :focus-visible didn't match if `preventDefault()` was called on the keyboard event. Now the model is that any trusted keyboard event will set had_keyboard_event to true, and any focus from mouse will re-set it to false. Bug: 1010549 Change-Id: Ifcb9bfbef746b91d99fc8ef42a8ef0e223fca2c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863061Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Cr-Commit-Position: refs/heads/master@{#707709}
-
Yusuf Sengul authored
When GCPW login is enforced, the reason may be due to not enrolled with mdm, missing encrypted password or expired session token. This change intends to reflect the reason in login screen instead of providing a generic message. Bug: 1014658 Change-Id: I92f4068ce71c8517fc41728c8909d86d736e2dc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862854 Commit-Queue: Yusuf Sengul <yusufsn@google.com> Reviewed-by:
Tien Mai <tienmai@chromium.org> Cr-Commit-Position: refs/heads/master@{#707708}
-
Minggang Wang authored
As the ad delay throttle has been removed, this util used for its unit test should be removed accordingly. Bug: 829042 Change-Id: Iddfaf10da02082eb0d2dad6ccf64577c2e0ce377 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867891Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Minggang Wang <minggang.wang@intel.com> Cr-Commit-Position: refs/heads/master@{#707707}
-
Tetsui Ohkubo authored
When the split view has been enabled and tablet -> clamshell switch happens, a snapped window should remain snapped. This capability was disabled for ARC apps in https://crrev.com/c/1435437 because ARC side support was not ready. As now the issue has been resolved, this CL re-enables the capability. A Tast test covering this case will be added. TEST=manual TEST=ash_unittests pass BUG=b:140498729 BUG=922282 Change-Id: I377ade04dc3181407b5073df24bc4621cd188b2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868729 Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Stefan Kuhne <skuhne@chromium.org> Cr-Commit-Position: refs/heads/master@{#707706}
-
Fergus Dall authored
Bug: 1015341 Change-Id: I711702f6e7ba4f5881bc227ab04f695e494c47fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868771 Auto-Submit: Fergus Dall <sidereal@google.com> Commit-Queue: Nicholas Verne <nverne@chromium.org> Reviewed-by:
Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#707705}
-
Chih-Yu Huang authored
Originally, VideoDecoderPipeline delegates VD tasks to the client thread. Each VD implementation then post the tasks to decoder thread. Then VD implementations post the callback back to the client thread when the task is done. In the future, ImageProcessor will also operate on the decoder thread. We will pass the task and output frames by: VDPipeline (client) -> VD (client -> decoder -> client) -> VDPipeline (client) -> IP (client -> decoder -> client) -> VDPipeline (client) -> Converter (client -> GPU -> client) -> VDPipeline (client) Total 6 thread hopping. This CL now posts the VD task on the decoder thread. We don't need to hop thread inside each VD implementation. With this CL, we could save 2 thread hopping. VDPipeline (client -> decoder) -> VD (decoder) -> VDPipeline (decoder) -> IP (decoder) -> VDPipeline (decoder) -> Converter (decoder -> GPU -> decoder) -> VDPipeline (decoder -> client) Total 4 thread hopping. BUG=chromium:998413 TEST=run video_decode_accelerator_tests on Eve and Kevin with dcheck_always_on = true Change-Id: I7367663258adfd0f46ddca25493faff4633ae034 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1777449 Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Reviewed-by:David Staessens <dstaessens@chromium.org> Reviewed-by:
-
Bettina authored
Bug: 1015618 Change-Id: Ica34fa1d574117c946b861d79e7d907326e13bc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867302Reviewed-by:
Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Bettina Dea <bdea@chromium.org> Cr-Commit-Position: refs/heads/master@{#707703}
-
DongJun Kim authored
In the past, "content/*/file_system" was renamed to "fileapi" to contain both the code for the filesystem API and the blob system. But the blob system moved out to separate directories, we have the confusing situation that we have directories named after one API that contain the implementation of a different API. This patch rename "storage/browser/fileapi" to "file_system" to actually match for reducing confusion. Bug: 921260 Change-Id: I18a391b43c054e647d938832f2055580a083437a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1858542 Commit-Queue: DongJun Kim <djmix.kim@samsung.com> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Reviewed-by:
-
Hirokazu Honda authored
VAContext of VaapiWrapper for VPP and VABuffer for BlitSurface are created on creating (i.e. VaapiWrapper::Create()). On the other hand, VAContext of VaapiWrapper for other use cases (e.g. video encoding) is created by VaapiWrapper::CreateContext() or VaapiWrapper::CreateContextAndSurfaces(). This leads a problem that VaapiWrapper for VPP cannot create surfaces because Context is already created upon calling VaapiWrapper::CreateContextAndSurfaces(). This CL removes the implicit context and buffer allocation on the creation. Therefore, a creator of VaapiWrapper for VPP has to call CreateContext() or CreateContextAndSurfaces() if the client wants the VaapiWrapper to create va surfaces. Note that an allocation of a buffer for BlitSurface is moved to VaapiWrapper::BlitSurface(), which is still implicit. Bug: 1009297, 1005205, 982201 Test: https://appr.tc/?debug=loopback&vsc=vp8&video=maxWidth=640,maxHeight=360,minWidth=640,minHeight=360&debug=loopback Test: tast run video.EncodeAccelH264* video.DecodeAccel* camera.* Change-Id: Ida5c4bfa58127674d4e048fedf9749516d89cd98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863056 Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#707701}
-
Hirokazu Honda authored
Bug: 1011281 Test: image_processor_test on atlas (crrev.com/c/1864758) Change-Id: I0ec6e5baee9a77ba5598b6f89d005ed41f16fc0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864501Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/f939cb63fdde..68591effc086 git log f939cb63fdde..68591effc086 --date=short --no-merges --format='%ad %ae %s' 2019-10-21 jmadill@chromium.org Vulkan: Store ImageView access in the graph. Created with: gclient setdep -r src/third_party/angle@68591effc086 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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=jmadill@google.com Bug: None Change-Id: I3149a9b82b5539e8cd42c7441e8884f8a26b1abf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870600Reviewed-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@{#707699}
-
Jeevan Shikaram authored
This CL adds aria-hidden tags to elements such as icons and headings that do not need to be read out by chromevox. It also adds an aria-label for the search field. Bug: 1001385 Change-Id: I9fc0ffef28902254000db95bfb177238e575ec74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1861439 Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org> Reviewed-by:
-
Marina Sakai authored
The comment "This key is used for uniquely identifying v8::Private." is repeated everwhere we define a private property key. This CL deletes the repeated comments by adding comments for the private property key in new API created in CL1810511. Bug: 715418 Change-Id: I6e95e826956c90e73c6343895746b7692a337224 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868530Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Marina Sakai <marinasakai@google.com> Cr-Commit-Position: refs/heads/master@{#707697}
-
Will Harris authored
A data encryption key is stored in profile and encrypted with DPAPI. DPAPI is needed during initialization but not during encrypt/decrypt operations. Data encrypted with the new key has a header to indicate the correct key to use, or whether it was originally encrypted with raw DPAPI. This allows code that uses os_crypt to run inside the sandbox as long as Init() is called before lockdown, or the key is manually set by calling SetRawEncryptionKey(). The network process, which uses os_crypt to encrypt some cookies, is now passed the encryption key via the mojo SetEncryptionKey interface, which is already used on macOS for the same purpose. NOTE: Reverting this CL will cause user data loss so please consult before doing so. BUG=1000799 Change-Id: I4453c4efbe52eaf4a264e12eb789219578e9caa6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842671Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#707696}
-
Charles Zhao authored
Bug: 1012936 Change-Id: Ibee8c1e8aa77d3eb034a9e16d30dc3ca1ced6865 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866115Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Tony Yeoman <tby@chromium.org> Reviewed-by:
Charles . <charleszhao@chromium.org> Commit-Queue: Charles . <charleszhao@chromium.org> Cr-Commit-Position: refs/heads/master@{#707695}
-
dalyk authored
Construct DoH requests using the new disable_secure_dns URLRequest field. Navigations to hostnames that happen to also be DoH hostnames will no longer be unnecessarily downgraded. Change-Id: I769dec1767a5af044bcddc2563d05d6ee999be51 Bug: 985589 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1843332Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Katharine Daly <dalyk@google.com> Cr-Commit-Position: refs/heads/master@{#707694}
-
Alex Danilo authored
Extends panel item testing for all remaining panel types. Exercises the signal callback handler for each panel type to verify correct operation. Bug: 1009318 Tests: browser_tests --gtest_filter="FileManagerJsTest.FilesDisplayPanel" Change-Id: Iae4c25bd7707d7a6d869e5f81a5e0963b3d73307 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865739 Commit-Queue: Alex Danilo <adanilo@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#707693}
-
- 20 Oct, 2019 16 commits
-
-
Charles Zhao authored
Bug: 1012936 Change-Id: Ia72d9f9fd424940ef09bade1b2b47c274f2b0592 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866226 Commit-Queue: Charles . <charleszhao@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#707692}
-
Jay Harris authored
Previously, shortcut creation was handled by the InstallFinalizer. This CL moves that responsibility to the AppShortcutManager. Bug: 860581 Change-Id: I8407977f35ace22772fcd2729a85cc11422d47ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862876 Commit-Queue: Jay Harris <harrisjay@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#707691}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/beacd8c81554..f939cb63fdde git log beacd8c81554..f939cb63fdde --date=short --no-merges --format='%ad %ae %s' 2019-10-20 jmadill@chromium.org Revert "Reland "Add more test_utils functions."" 2019-10-20 jmadill@chromium.org Reland "Add more test_utils functions." Created with: gclient setdep -r src/third_party/angle@f939cb63fdde If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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=jmadill@google.com Bug: chromium:1015810,chromium:1015810 Change-Id: Ic98b3aa844b49ce5ecd01ac203a8d47befe4fa64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870597Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/609ad8c3a60f..ff3029411808 git log 609ad8c3a60f..ff3029411808 --date=short --no-merges --format='%ad %ae %s' 2019-10-20 vapier@chromium.org ts_mon: basic python3 porting for import Created with: gclient setdep -r src/third_party/chromite@ff3029411808 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I73636ee4bb3ae3feff6b4b8fb7267a9ba1800bd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870595Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: If0b6627ebaa5709ee6feb25e8004f4bb1bf817b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870969Reviewed-by:
-
Joel Hockey authored
Add check for browser tab drag to only allow between apps with the same name. New feature flag MixBrowserTypesTabs will allow tabs of any browser types or apps to mix. It is disabled by default. Bug: 1012169 Change-Id: Ib525f5008e7585e063ddcd9af70f08a39b71f5f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868215 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#707687}
-
Joel Hockey authored
Apps with tabs require the extra height (42px vs 35px) in order for the tabs to display correctly. Also changed apps with tabs to use default color scheme for tabs rather than having only a single color across the entire frame so that fg vs bg tabs are easily detected. Bug: 1015624 Change-Id: I22a08ee24910ad2c3c6cd40680410be5fc7a7643 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868209Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#707686}
-
Paul Moy authored
Migrate the battery metric collection from runtime_probe to cros_healthd. manual testing, where I cherry-pick crrev.com/c/1779132 and checked /var/log/chrome/chrome for the expected values. Bug: b:128683357 Test: DeviceStatusCollectorTest.TestCrosHealthdInfo and Change-Id: Ia0290d189d7eabf1ec8e878edcd4f56b7025bb04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847177Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Jorge Lucangeli Obes <jorgelo@chromium.org> Commit-Queue: Paul Moy <pmoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#707685}
-
Maksim Sisov authored
This is a reland of 6983e9fa Change: provided a correct include Original change's description: > X11 and Ozone: Move static methods to DWTHLinux. > > At first, I wanted to remove these static methods, but then decided > to keep them and remove later when we no longer need them. > > Bug: 990756 > Change-Id: If6132986e25bb1c8712acdbc90ce29093616bff7 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860341 > Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Commit-Queue: Maksim Sisov <msisov@igalia.com> > Cr-Commit-Position: refs/heads/master@{#705946} Bug: 990756 Change-Id: Ifc7dc9675aeb0ce9ebf938f1c4660f3d312dbb62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868869 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#707684}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/d739727b79ee..beacd8c81554 git log d739727b79ee..beacd8c81554 --date=short --no-merges --format='%ad %ae %s' 2019-10-20 jmadill@chromium.org Vulkan: Rename format fields. Created with: gclient setdep -r src/third_party/angle@beacd8c81554 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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=jmadill@google.com Bug: None Change-Id: I85469a61586e5153d1e02fa9a8344ad1267d58fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869841Reviewed-by:
-
Huanzhong Huang authored
In the goal of cookie controls UI getting hidden when (the original) third-party cookie blocking is either managed or turned on by User, this change covers the (previously overlooked) cases where 3p cookie blocking's managed state goes from managed to unmanaged and vice versa. Bug: 967668 Change-Id: I299b4054fe9b89287f7bf39ccd726454f3aaeda8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866713 Commit-Queue: Huanzhong Huang <huanzhong@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#707682}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: If707ab3fe0be284b523496e870c6bcff7c7fc7cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870686Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/016347045072..d739727b79ee git log 016347045072..d739727b79ee --date=short --no-merges --format='%ad %ae %s' 2019-10-20 jmadill@chromium.org Remove Vulkan repos from exec script whitelist. Created with: gclient setdep -r src/third_party/angle@d739727b79ee If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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=jmadill@google.com Bug: None Change-Id: If603f033a124550635626329873625071b6d4667 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870610Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/73206e3b8478..609ad8c3a60f git log 73206e3b8478..609ad8c3a60f --date=short --no-merges --format='%ad %ae %s' 2019-10-20 vapier@chromium.org buildbucket_v2/ts_mon: temporarily hack import paths for protobufs Created with: gclient setdep -r src/third_party/chromite@609ad8c3a60f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: Ide430a728ccbc6b616f02055f12869510acbef32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870593Reviewed-by:
-
Daniel McArdle authored
In the attached bug, the query_parser::ParseQueryImpl function is timing out after 25 seconds while parsing a large input (109K). The problem appears to be that the ICU function |ubrk_next| is a little slow. There isn't anything obvious we can do to improve performance, so we will now reject inputs that are larger than ~1/2 of the "bad" input's size. Bug: 1015888 Change-Id: Icd3b1bcf30714fd39ef6700e0f44fbf09efa3c82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869771Reviewed-by:
-
Scott Violet authored
Deprecated flex box only considers box-pack if there is remaining space (https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/renderer/core/layout/layout_deprecated_flexible_box.cc#1053 ish). This patch makes it so flex box does the same if it's emulated -webkit-box. BUG=1014884 TEST=wpt/compat/webkit-box-ignore-box-pack.html Change-Id: Ic15d1f93957ba8923c48e5a3a9864f17af412a17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864321 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#707677}
-
