- 08 Oct, 2020 40 commits
-
-
Swapnil authored
We want to investigate why the force installed extensions fail to install with error CRX_HEADER_INVALID. This CL adds UMA statistics to record whether the extension is from Chrome Web Store or not when extension fails with CRX_HEADER_INVALID error to get more details about it. New histogram added: "Extensions.ForceInstalledFailureWithCrxHeaderInvalidIsCWS" Bug: b/170080693 Change-Id: I5cbaef996151fa75aa5716c985c5ce2035a04ac1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449334 Commit-Queue: Swapnil Gupta <swapnilgupta@google.com> Reviewed-by:
Oleg Davydov <burunduk@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#815097}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/5f4e70b81046..952149303d06 2020-10-08 bclayton@google.com SpirvShaderDebugger: Have Function inherit LexicalBlock If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I0b653f86c4dc5301e5c590bc43b363a6ab622bbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460869Reviewed-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@{#815096}
-
Eric Willigers authored
DesktopPWAsWithoutExtensions has shipped. The test no longer needs to be parameterized Bug: 1065748 Change-Id: I8005d00dc569fb63d1b3ca5f9856308a7216a88d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2455787 Commit-Queue: Sergey Poromov <poromov@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#815095}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/24d353df49fd..b8389aa11092 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC olka@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: olka@google.com Change-Id: Ie75feda03fb3cf636b770454455e9e8a99733b0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460870Reviewed-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@{#815094}
-
Maksim Sadym authored
content_shell uses `ExecuteJavaScriptMethod` instead of `ExecuteJavaScriptForTests`, which should reduce serialisation/deserialisation overhead. The improvement for test run in `third_party/blink/web_tests/http/tests/devtools` is 2.02s (~1.2%). 95% confidence interval of this difference: From 0.3398 to 3.6936 Bug: chromium:1029427 Change-Id: Iba108d23192bde0fa12aa66654271cd85c5e4ada Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2452670 Commit-Queue: Maksim Sadym <sadym@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#815093}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/acdf3c1947a2..56df381f7893 2020-10-08 dberris@chromium.org [pinpoint] Support Monorail projects in UI If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC zhanliang@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-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:1111450 Tbr: zhanliang@google.com Change-Id: I27ecfdcf1abb0d26188bcc1305325fe4b4cf1a33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459897Reviewed-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@{#815092}
-
Bret Sepulveda authored
This removes part of permission prompts' dependency on PermissionRequest, with the goal of eventually moving the latter's functionality into the UI layer. Bug: 1110905 Change-Id: Icf53d3774c7415453c2266a0db07622483e7b197 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367836 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
Olesia Marukhno <olesiamarukhno@google.com> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#815091}
-
Tim van der Lippe authored
This is required for landing https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2450036 R=szuend@chromium.org Bug: 1011811 Change-Id: Iff89f391e7bfa238c4eaeeb5e1ddc4efad19bd05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461267 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by:
Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#815090}
-
Gauthier Ambard authored
The flag has been removed for a while, I forgot to remove the entry when removing the flag. Bug: none Change-Id: I5c733e1e659f30b6f003b2879be08e80f15af99c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460810 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Auto-Submit: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#815089}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/1a87f1f025ef..6a09a9d46097 2020-10-08 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from a5a8696e to 090102a7 (466 revisions) 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 timvp@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/+doc/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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: timvp@google.com Change-Id: I0929a8a6c8a6b8f3da6ef2963dd50850eb9c35b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461047Reviewed-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@{#815088}
-
Wei Lee authored
It can help to boost the development when simply changing JS/CSS/HTML on CCA (SWA). Bug: 1127459 Test: cca deploy-swa [BOARD] [DEVICE] Change-Id: I3f494a8d455b4c5632f91942f95b428b03294af9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2456706Reviewed-by:
Shik Chen <shik@chromium.org> Reviewed-by:
Inker Kuo <inker@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#815087}
-
Chris Thompson authored
This is an initial solution for crbug.com/1129197 -- the full solution is implemented in crrev.com/c/2422435 but requires changes to allow mocking CT results in order to land. This prevents logging private certificates, and adds a test explicitly exercising this case. It also makes the browser tests a bit more robust by tracking the last report seen by the test server and adding a step to flush a new report through for negative tests. Bug: 1129197 Change-Id: I7e1d4010b2666db7f98194aa1e3ba80df1e0a493 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2453777Reviewed-by:
Emily Stark <estark@chromium.org> Reviewed-by:
David Schinazi <dschinazi@chromium.org> Reviewed-by:
Nick Harper <nharper@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Chris Thompson <cthomp@chromium.org> Cr-Commit-Position: refs/heads/master@{#815086}
-
Gauthier Ambard authored
This CL removes dead code. Bug: none Change-Id: I35604f094924f30b6f342979369f8bbd8e089f3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424250 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Reviewed-by:
David Jean <djean@chromium.org> Cr-Commit-Position: refs/heads/master@{#815085}
-
Tanmoy Mollik authored
The sync row should launch signin flow if the user is signed in but did not give sync consent. This cl adds tests for that behavior. Bug: 1135686 Change-Id: If90233ca63ab0b9ad69121e2d68ae2c1e5f84c4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2454129 Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#815084}
-
Rohit Agarwal authored
The test logic before was counting the incognito notifications after having opened incognito tabs. However, that resulted in flakiness as sometimes we have two notifications for two incognito tabs and some other time we have only one notification. This CL instead of verifying the count of the notification displayed, relies on verifying whether there exists a notification which matches the StatusBarNotification#getTag with that of IncognitoNotificationManager#INCOGNITO_TABS_OPEN_TAG. Bug: 1134241 Change-Id: Iaf80ab369b29e2efcd124f7980f3b1ccba5f76c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2452472 Commit-Queue: Rohit Agarwal <roagarwal@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#815083}
-
Felipe Andrade authored
This work is been done in preparation for enabling Kerberos on MGS. See associated bug for further details. Bug: 983041 Change-Id: I4b351941bab4312067bcd7d687c62639259e5d59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459367Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Felipe Andrade <fsandrade@chromium.org> Cr-Commit-Position: refs/heads/master@{#815082}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/38e6d226f24e..ac0723a06b53 2020-10-08 skia-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 635de036d766 to 5f4e70b81046 (1 revision) 2020-10-08 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 3c775217 to af82ff26 (468 revisions) 2020-10-08 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 7e22b1c44fb0 to 6b4a4a85dfd7 (9 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC jvanverth@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: jvanverth@google.com Change-Id: I9f8a3039e5fec20bc45f03fe69bfbae14832d60c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460565Reviewed-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@{#815081}
-
Eric Willigers authored
DesktopPWAsWithoutExtensions has shipped. The test is no longer needed. Retiring the test also closes flaky test bugs. Bug: 1065748,1043466,1043806,1044900 Change-Id: I1344f2a2373ead35cf0700a26cdbf1af713e7bc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2455567Reviewed-by:
Alan Cutter <alancutter@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#815080}
-
Rainhard Findling authored
Bug: 1087263 Change-Id: I38fe5c305a2726e5600770adeffba26b031d99a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2445930Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#815079}
-
Alison Maher authored
In CL:2422213, the previous break token was stored as a reference in NGBoxFragmentBuilder. This change cleans up functions that take both as arguments since we can now access the break token from the builder. The only function where this was the case was FinishFragmentation(). No functional change. Bug: 829028 Change-Id: If9ea5a7ed937e9c2c127ae541b5c4de21dfed4f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458781Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#815078}
-
Jérôme Lebel authored
ChromeIdentityService::GetIdentityWithEmail() is unused. The implementation is removed with: crrev.com/i/3318008. Change-Id: I8926f60be9bfd18814b1fc2aaadf4a3f9321c5dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2455607Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#815077}
-
Ioana Pandele authored
This is no longer useful. Bug: 1125735 Change-Id: Ib55174f552fcf6e05f72ee5db13ad24a18b51751 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440891Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#815076}
-
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/+doc/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: I849115f4af41f6c639f8424ae5cb868590501295 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460867Reviewed-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@{#815075}
-
Kent Tamura authored
The function iterates over RootInlineBoxes, which are not used in LayoutNG. This CL adds LayoutNG FragmentItem support to ValueWithHardLineBreaks(). The new code in ValueWithHardLineBreaks() is almost equivalent to the existing NodeTraversal loop, and this CL introduces GetNextSoftBreak() function for FragmentItem. This CL fixes textarea-wrap-submission-value.html test with LayoutNGTextArea flag, but this doesn't change any user-visible behavior yet. Bug: 1040826 Change-Id: Ice5e3954df7cd0f8ccb4f1e94d9057be5cbcc3cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2454893Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#815074}
-
Hidehiko Abe authored
The feature is not for Chrome OS. Remove it from Chrome OS. This is also for the preparation to unset OS_LINUX for Chrome OS build. With this CL, the part will not be affected on switching. Bug: 1110266 Test: Built locally. Change-Id: Ia22a2dff5cc82e223559abc11e76171c739f03dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2452030 Commit-Queue: Hidehiko Abe <hidehiko@chromium.org> Auto-Submit: Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#815073}
-
Paula Vidas authored
The FakeInstanceIDDriver needs to be used in sync invalidations tests. Bug: 1135167 Change-Id: Ifa5c38ea18317d7b99635fee6ee12e129bf4dda8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2455646Reviewed-by:
Rushan Suleymanov <rushans@google.com> Reviewed-by:
Marc Treib <treib@chromium.org> Commit-Queue: Paula Vidas <paulavidas@google.com> Cr-Commit-Position: refs/heads/master@{#815072}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/cdd72c9222b3..1e48b0c6724e 2020-10-08 alexrudenko@chromium.org Migrate ProtocolMonitor.js to TypeScript 2020-10-08 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+doc/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I0b50734c723072ff47a17c8a2881b7e115b77f2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459192Reviewed-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@{#815071}
-
Yoshifumi Inoue authored
This patch makes |LayoutText::PositionForPoint()| to find text fragment considering line height to return valid |Position| for point between lines. Example: <style> #container { font-size: 10px; line-height: 3; font-family: Ahem; width: 5ch; // to break line after "line1" } </style> <div id=container>line1 line2</div> In this example, we have two line boxes: line1 box: {0,0}x{50,30} "line1" {0,10}+{50,10} line2 box: {0,30}x{50,30} "line2" {0,10}+{50,10} Before this path, |LayoutText::PositionForPoint({10,30})| returns "line1 line2"[0] instead of "line1 line2"[7] because text fragment "line2" doesn't contains {10,30}. After this patch, we find the line contains {10,30} then locate fragment in line by using inline offset e.g. x-coordinate for horizontal writing mode, y-coordinate for vertical writing mode. Bug: 1133786 Change-Id: I7f76aadf6e1be4c3d8517562242158fadf5f2876 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2452169 Commit-Queue: Koji Ishii <kojii@chromium.org> Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#815070}
-
Julie Jeongeun Kim authored
The request id could not be set from PrintRenderFrameHelper when it calls PrintPreviewFailed(), PrintPreviewCancelled(), or PrinterSettingsInvalid() as the request id is set from |print_pages_params_| and it could be null. This CL adds early return when the request id is -1. Bug: 1136025 Change-Id: I06caaef4050653ddb9ff82b477a74600e9796a55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2455826 Commit-Queue: Julie Kim <jkim@igalia.com> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#815069}
-
Rainhard Findling authored
Bug: 1087263 Change-Id: If6f8928141ee1569cf522fe738403143a4197bbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442735Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#815068}
-
Alan Screen authored
Adding support for PrintBackend queries to happen out of the browser process requires related data structures to be made available via a Mojo interface. These are moved into their own mojom file separate from the common definition in printing/mojom since they are specific to a new process being introduced and do not need to be encumbered by the dependencies which exist for print.mojom. Starting with the historically most prolific cause of browser crashes from printing (GetPrinterSemanticCapsAndDefaults), work towards having support definitions to enable that query to be moved out-of-process. Add the mojo definition for PrinterSemanticCapsAndDefaults to expose the needed structure for the query. Bug: 809738 Change-Id: Idf971066982ff989668e1b227276b13844e7a054 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387545 Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#815067}
-
Bettina Dea authored
After clicking on the Enhanced Protection promo on desktop, the Security settings page should open with the Enhanced Protection section expanded. Bug: 1130722 Change-Id: I646566199755862055e8be0fba00259ecf48d704 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2454404Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Bettina Dea <bdea@chromium.org> Cr-Commit-Position: refs/heads/master@{#815066}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I58b94352a5f4cb28c144f5b2089a91caecb4c3b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460752Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#815065}
-
Hidehiko Abe authored
Currently OS_LINUX is defined on Chrome OS build, but it will be unset. This is preparation ot keep the current behavior. Bug: 1110266 Test: Built locally. Change-Id: Ia587de5b23cbe6e6622c0a9aaa918880d9762d45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449654Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Auto-Submit: Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#815064}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1602115190-7131f9189957170a35177f66dc087c48158aec91.profdata to chrome-linux-master-1602136563-0d72642499ba1a8379313d017bceff00a59e9e7c.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I030a5a8ab31eacb7d2f486660aef3d6970f93b60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460240Reviewed-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@{#815063}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1602115190-6522495ca352d45be49e234f0c6bf7d20bdcb906.profdata to chrome-mac-master-1602136563-35c37307a75e48d8d50dea3abef2bbe00d3f301f.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I7fd3bf5cf8996187a2376379235daa21fafe630a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2460550Reviewed-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@{#815062}
-
Takashi Sakamoto authored
If use_ozone=true or use_x11=true, we need //ui/base:features. Change-Id: Id3ba57d5205c17de3c1f10230639e58131e8ea93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459945Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Takashi Sakamoto <tasak@google.com> Cr-Commit-Position: refs/heads/master@{#815061}
-
Felipe Erias authored
Update LayoutBlockFlow::DetermineLogicalLeftPositionForChild to correctly take into account all the cases where the width of the logical left scrollbar may be different from 0. This fixes a problem where the "both" value of scrollbar-gutter was producing the wrong layout when LayoutNG was disabled. Bug: 710214 Change-Id: If3481ff2486fc3a7a447b892edc8ef98fa658f1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459793Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Felipe Erias Morandeira <felipeerias@gmail.com> Cr-Commit-Position: refs/heads/master@{#815060}
-
Reilly Grant authored
This changes the documentation for the WebUsbAllowDevicesForUrls policy to clarify when it is referring to a field in the JSON object that must be specified by the administrator. Bug: b:170255974 Change-Id: I23cdfa5fecdc8001df8d195fc1c63a529d60bc81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459935 Auto-Submit: Reilly Grant <reillyg@chromium.org> Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#815059}
-
Colin Blundell authored
//chrome currently defines and tracks metrics related to user interactions with the subresource filter feature. This CL componentizes the definition of these metrics in advance of componentizing some of the code doing the tracking (e.g., the ads blocked infobar) for reuse in WebLayer. Bug: 1116095 Change-Id: If9033d2aa4e2714b4610974409d1fdb179578740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2456608Reviewed-by:
Eric Robinson <ericrobinson@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#815058}
-