- 13 Mar, 2020 40 commits
-
-
Nathaniel Steinbock authored
Merge-With: eureka-internal/372572 Bug: internal 150884605 Change-Id: I3ebfba162fda3a8e36c431420afb1d2054162672 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096895Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Commit-Queue: Nate Steinbock <steinbock@google.com> Cr-Commit-Position: refs/heads/master@{#750310}
-
Philip Rogers authored
This was added in https://crbug.com/470640 which predated the cc scroll tree. Change-Id: If47c0665f90b16f5b134d81d2388c1349af77cd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102628Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#750309}
-
Joe DeBlasio authored
Before this change, we could not disambiguate when users saw the UI (in the treatment group) from the equivalent "first visit" in the control group. This is because subsequent page visits in the control group were still flagged with the original "bad reputation" or "lookalike" flag. This CL makes it easier to compare between control and treatment groups by automatically setting the 'ignored' flag for a given URL after the first visit if the UI is not enabled. Previously, this state was never used in the control group. This CL is not user visible, since it only impacts the control group, and the control group sees no UI. Bug: 1061254 Change-Id: I2e4bd626d1b7b81d675259d7555f15604fda43e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101932 Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#750308}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9fd413dec7c0..3ef483f4c980 git log 9fd413dec7c0..3ef483f4c980 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 bsheedy@chromium.org [Telemetry] Enable leftover minidump catching Created with: gclient setdep -r src/third_party/catapult@3ef483f4c980 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 rmhasan@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: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:1056235 Tbr: rmhasan@google.com Change-Id: Iceb475bb6a47925b63055a3fc8b6531bf87ca754 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103350Reviewed-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@{#750307}
-
Chris Blume authored
Currently, the tests for always-wide and dynamic-wide are separate. A bug was found and fixed [1] where the always-wide support wasn't being checked when dynamic-wide was enabled. This CL returns false in the dynamic-wide test if always-wide is enabled. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2102777 Bug: 955158 Change-Id: I7c5ce5dd2f7704687dee5753d699557450edb177 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103138Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Chris Blume <cblume@chromium.org> Cr-Commit-Position: refs/heads/master@{#750306}
-
Henrique Ferreiro authored
Add missing calls to WebView::DidAttachLocalMainFrame() after setting up the local main frame for a given web view. Bug: 1053546 Change-Id: If74dcc23b91dd5218c526d48a6b49b84d4b809dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102571 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#750305}
-
Dave Tapuska authored
Move the queueing of the swap promise from RenderWidget into WidgetBase. This requires expose a callback AddPresentationCallback which will be eventually be removed when LayerTreeView moves into blink. Change-Id: I765d787bc6f1fd2246e142bc4c5a1ecc91ec79dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090461 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#750304}
-
Lei Zhang authored
If the printing sticky settings somehow ended up with "customMargins:null", then Print Preview code that assumes customMargins values are always valid will fail while reading properties of null. Change-Id: I8fb297e58050bf78605931c8aafb390035f486e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102083 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#750303}
-
Sophie Chang authored
Bug: 106426 Change-Id: Ia4b13ebbbc654e14fc547e3641e5b63938bbe173 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097365Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Sophie Chang <sophiechang@chromium.org> Cr-Commit-Position: refs/heads/master@{#750302}
-
Juanmi Huertas authored
Replacing instances of AcceleratedResourceUsage for SharedImage and Bitmap resource providers. Changing expectation of a test as this now should fail and not fallback into the Bitmap mode unless we explicitly call it. Adding a new SharedGPUContextTest with the Viz context system, to be able to validate the correct creation of a CanvasResourceProvider of SharedImage. Also modifying gpu_test_utils to set the context to not lost. Bug: 1035589, 1021287 Change-Id: I15342b57f3721bad7bb2b44af184c5b0ae8a4764 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095878Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Commit-Queue: Juanmi Huertas <juanmihd@chromium.org> Cr-Commit-Position: refs/heads/master@{#750301}
-
Haiyang Pan authored
Bug: 1032336 Change-Id: I246ddb83eba231100c84007c734a7865fd619be8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102076Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#750300}
-
Nate Chapin authored
Bug: 1061309 Test: fast/canvas/toBlob-in-detached-doument.html Change-Id: I3d515666c9228d6d32791bad588149f879020b2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103046Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#750299}
-
Joe DeBlasio authored
This CL is a small change that ensures lookalike sites that redirect to themselves still see the lookalike interstitial. Bug: 1056847 Change-Id: I52dce34ac6cb6818da638840057cf8f354c1da07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103072 Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org> Auto-Submit: Joe DeBlasio <jdeblasio@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#750298}
-
Nate Chapin authored
ExecutionContextLifecycleObserver::SetExecutionContext tolerates nullptr, but this override does not. Bug: 1061369 Test: fast/media/move-video-to-new-document-crash.html Change-Id: I0fd35fa5abb550187757cd932102b8e303be39bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103128Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#750297}
-
shrekshao authored
glTexStorage generates GL_INVALID_OPERATION for out of bounds level which is a bit different from other GL calls generating GL_INVALID_VALUE. So treat it as a special case. Restore what TextureManager::ValidForTarget used to be. Bug: 1061154, 1061534, 1061560 Change-Id: I69d8cc9c7170cf9346c2fb2f9edc1d87588fc039 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101715 Commit-Queue: Shrek Shao <shrekshao@google.com> Reviewed-by:
James Darpinian <jdarpinian@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#750296}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/83d503bc728e..b7902da1d4b4 git log 83d503bc728e..b7902da1d4b4 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 tsepez@chromium.org Cleanup CFX_CSSSyntaxParser. 2020-03-13 tsepez@chromium.org Cleanup CFX_CSSTextBuf. 2020-03-13 tsepez@chromium.org Consolidate some V8 type conversion code. 2020-03-12 thestig@chromium.org Remove unnecessary CheckedNumeric usage in CPDF_DataAvail. Created with: gclient setdep -r src/third_party/pdfium@b7902da1d4b4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@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 Bug: None Tbr: pdfium-deps-rolls@chromium.org Change-Id: I2615c6236f3f595fe441d2ef5c01feb6ea1bb077 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103262Reviewed-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@{#750295}
-
Robbie McElrath authored
browserservices.Origin is used by Chrome's site settings page, which is being componentized so it can be used by WebLayer. This CL moves the class to //components/embedder_support. Bug: 1058597 Change-Id: Ic47da47f372d1c27238efd2fee8d7bdcba6eb63d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090875 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#750294}
-
Lei Zhang authored
Combine a bool and a size_t into base::Optional<size_t>. Then only assign a value when the new variable will not underflow. While unsigned integer underflows are well defined, it is still better to not have them when possible. Also make IsDescendantOf() const along the way. Change-Id: I0b1a35b593e231dbd181dcbdc90496df6a7d31cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097119 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Adam Ettenberger <Adam.Ettenberger@microsoft.com> Reviewed-by:
Ethan Jimenez <ethavar@microsoft.com> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Chris Hall <chrishall@chromium.org> Cr-Commit-Position: refs/heads/master@{#750293}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/7011463f2d4a..06c8bce1482c git log 7011463f2d4a..06c8bce1482c --date=short --first-parent --format='%ad %ae %s' 2020-03-13 sokcevic@google.com Add unit tests for fetch.py Created with: gclient setdep -r src/third_party/depot_tools@06c8bce1482c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@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 Bug: None Tbr: agable@chromium.org Change-Id: I746e740d861942f002f90ee9b5041a78300cebf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103256Reviewed-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@{#750292}
-
Thomas Guilbert authored
This reverts commit bbe1b84e. Reason for revert: We no longer have 3 API OWNER LGTMS Original change's description: > [video-raf] Enable video-raf by default > > This CL turns on HTMLVideoElement.requestAnimationFrame() by default. > > Spec: https://wicg.github.io/video-raf/ > Blink-dev intent-to-ship: https://wicg.github.io/video-raf/ > WPT: https://wpt.fyi/results/video-raf > > Bug: 1012063 > Change-Id: I5f44a430078e8272d2f9ebb1482e11e936697fb5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101242 > Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> > Commit-Queue: Chris Harrelson <chrishtr@chromium.org> > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> > Cr-Commit-Position: refs/heads/master@{#749965} TBR=kbr@chromium.org,chrishtr@chromium.org,tguilbert@chromium.org Change-Id: I0af2785d83863dea9943a491c3679874de0b8cb8 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1012063 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103391Reviewed-by:
Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Cr-Commit-Position: refs/heads/master@{#750291}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/b1b6a171ee02..a8c95f74dac6 git log b1b6a171ee02..a8c95f74dac6 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 jmadill@chromium.org Update export_targets to fix presubmit on Windows. Created with: gclient setdep -r src/third_party/angle@a8c95f74dac6 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-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: jmadill@google.com Change-Id: Ie099dcff7b6f9a2d415dbff5b1e60c2d6e9fcb60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103044Reviewed-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@{#750290}
-
Aaron Leventhal authored
Any non-elements can use the standard layout tree builder traversal to find accessible children. Non-elements include text nodes, and most importantly, the #document node, which is the kRootWebArea. This change only affects <dialog>, but it's an improvement. Previously, a <dialog> would be added as a child in two places: - As a child of the root node, because of layout traversal - As a child within its actual DOM structure Fortunately, it does not show up in the Blink tree twice, because BlinkAXTreeSource has a !IsParentUnignoredOf() which ends up not adding the DOM structure <dialog> child. However, this double adding of children blocks landing of a chain of other fixes necessary to avoid accidental resets of the accessible tree during serialization. NOTRY=true Bug: None Change-Id: I1ebb0ee4d7cdaea285773d391b3e73c0f1ecdb6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101325 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#750289}
-
Tricia Crichton authored
Enable 2 tests to check an diagnose flakiness. Bug: 1036055, 1036636 Change-Id: I7f79bdf1b21bf29e393af2ea30e34c538ed94b11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103027Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Tricia Crichton <triciac@chromium.org> Cr-Commit-Position: refs/heads/master@{#750288}
-
Nico Weber authored
No behavior change. Bug: 346399 Change-Id: I9d9e855d94fc646faecd69580ef280a6763ba28b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102631 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#750287}
-
Sam Bowen authored
Bug: 1044253 Change-Id: I652f04d2e7ced7a5289a4d6d0dcef2e577e7a570 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076084 Commit-Queue: Sam Bowen <sgbowen@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#750286}
-
Christian Biesinger authored
If the override height is indefinite, this function should return true. This fixes the case of max-height: xx% on a replaced item in a flexbox, which otherwise would get resolved to 0 because resolving the percentage for replaced items would convert negative numbers to 0. Fixed: 1048051 Change-Id: I192e65b37a3670226fa764662448bdb4216c9fe1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100771 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
David Grogan <dgrogan@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#750285}
-
Johannes Henkel authored
Upstream PR: Introduce a crdtp/dispatch.{h,cc} library. https://chromium-review.googlesource.com/c/deps/inspector_protocol/+/1974680 New Rev: 8c2064ea99cffdb5647760ad3953c43e612e07fc Notable downstream changes: - ChromeDevToolsManagerDelegate::HandleCommand no longer carries a method. Reason being, the shallow parser (crdtp::Dispatchable) should be efficient enough to parse an incoming message a couple of times, e.g. once for the content layer and once for the embedder, and if we felt differently then we'd quite possibly want to carry more than just the method - e.g., we'd want to also pass the params. Anyway, for now simplifying this interface. - crdtp::FrontendChannel::FallThrough; here, it's advantagueous to keep the method around, but now it's a crdtp::span. This is much better than const std::string& because the generated code knows exactly which method is going to fall through and we can pass a C++ string literal via this span. - The crdtp/dispatch library presents a somewhat different surface between the UberDispatcher and the session implementations. The session implementations are responsible for creating a crdtp::Dispatchable instance (the shallow parser) which it then hands to the dispatcher for dispatching. Rather than querying for whether it can dispatch and then doing it, the result of the Dispatch indicates whether a method was found and can be executed. There's no more need to instantiate protocol::Value in a devtools session class. - Since the dispatch library uses crdtp::span to represent method names, we no longer need to reference platform specific routines for finding strings and making substrings. As a result, v8_inspector_string.h is losing a few more methods (and same for base_string_adapter_h.template). - crdtp::DispatchResponse (also known as protocol::Response) has some renames for consistency ( Response::Error -> Response::SeverError, Response::OK -> Response::Success). Touches all domain handlers but is mechanical. - All protocol error messages, such as the parameters passed to DispatchResponse::ServerError are required to be UTF8 strings, even for Blink, so when code generates them as WTF::String, we convert them to std::string using WTF::String::Utf8() before passing them to DispatchResponse::ServerError. - We're better about checking messages and sending errors when we can't parse them - esp. we no longer drop messages on the floor if we can't make sense of them; the LOG statements are gone, because we can either send an error or assume that we've previously parsed the message elsewhere and put a DCHECK (e.g., a message received by blink has always been shallow-parsed by the browser before). - DevToolsAgentHost::DispatchProtocolMessage no longer has a boolean return value. Reason being, it's not well defined what the boolean should indicate. If we reject the message and send an error, arguably we've also handled it. And of course, we always do that (now). So it's not useful to generate or check this return value, and there is only one DCHECK on it currently, which is also not covered by tests. - content::DevToolsSession uses binary searches to match method names (e.g. in ShouldSendOnIO). This is because I've switched the method names to span, and implemented similar searches for the dispatching library, so it's best to be consistent. It will also scale better if we add more methods. - The additional unittests added to the CRDTP library upstream cover shallow parsing, dispatching, etc. and are now also part of the content_unittests. - Improves Android binary size by about 36k, by reducing code duplication. There's now just one UberDispatcher, for example, as opposed to one for blink, one for content, one for headless, one for chromium, ... - Speeds up execution by 1-2% (based on internal measurements), because message serialization no longer takes a detour via protocol::Value. Change-Id: I422fe527d6f8a6ffb098b3992728ecba408b571f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047966Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#750284}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/b8bae186cbec..be4a731fe43b git log b8bae186cbec..be4a731fe43b --date=short --first-parent --format='%ad %ae %s' 2020-03-13 amaiorano@google.com BUILD.gn: add missing dependency onto marl for SubzeroReactor 2020-03-13 capn@google.com Consistently use TRUE/FALSE in CMakeLists.txt 2020-03-13 capn@google.com Exclude all static libraries from "all" build target 2020-03-13 amaiorano@google.com Subzero: replace Win32 fibers with Marl for couroutines Created with: gclient setdep -r src/third_party/swiftshader@be4a731fe43b 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/+/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 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I5d3191fc206d56ba3f28363c452c1186cfcf697a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103041Reviewed-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@{#750283}
-
Shimi Zhang authored
- addWebMessageListener() - removeWebMessageListener() Bug: 918065 Change-Id: Id271f328224942edb962a29fe44617240aa18a5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099233Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Commit-Queue: Shimi Zhang <ctzsm@chromium.org> Cr-Commit-Position: refs/heads/master@{#750282}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/b45bb3bba858..9fd413dec7c0 git log b45bb3bba858..9fd413dec7c0 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 crouleau@chromium.org [Catapult] Update OWNERS files. Created with: gclient setdep -r src/third_party/catapult@9fd413dec7c0 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 rmhasan@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: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:949246 Tbr: rmhasan@google.com Change-Id: Ie9cfaab0feea3e0826e0f88a2aff48f8f53160fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103251Reviewed-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@{#750281}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/0bbeee05c7a1..a7657e4fa2fe git log 0bbeee05c7a1..a7657e4fa2fe --date=short --first-parent --format='%ad %ae %s' 2020-03-13 rharrison@google.com Rolling 2 dependencies (#999) Created with: gclient setdep -r src/third_party/shaderc/src@a7657e4fa2fe If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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 Bug: None Tbr: radial-bots+chrome-roll@google.com Change-Id: I75760ddabeda32191e167c91be8ac38f866059c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103042Reviewed-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@{#750280}
-
Andrew Xu authored
Bug: 1058589 Change-Id: I4b3685014e7714b42aa65640890d94fbdbd4f5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102639 Commit-Queue: Andrew Xu <andrewxu@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750279}
-
Benoit L authored
This reverts commit 8e6f8572. Reason for reland: The dependency which broke was removed in https://chromium-review.googlesource.com/c/chromium/src/+/2093606 Original change's description: > base/android: Remove linker tests support. > > The linker tests don't run on bots (and likely not locally either) and > do not support the latest library loading patterns. This is the first > step to remove them, as they add non-trivial complexity in the codebase. > > Bug: 1059707 > Change-Id: Ia14693419792f57dc4f65b2fc7f999e833aec42e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095059 > Reviewed-by: Yaron Friedman <yfriedman@chromium.org> > Reviewed-by: Egor Pasko <pasko@chromium.org> > Commit-Queue: Benoit L <lizeb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#748365} Bug: 1059707 Change-Id: I3ad7347fdf4868d83ebf1895bee1bd85940ea324 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098785Reviewed-by:
Egor Pasko <pasko@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#750278}
-
Piotr Bialecki authored
Change-Id: I845e082ca413bcfa19a5ca4e06f587ebcb2cb254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101713 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#750277}
-
Daniel Rubery authored
Enterprise deep scanning for DLP violations has a specific list of supported file types and the policy BlockUnsupportedFiletypes should determine whether to blocked files not on that list. This CL introduces a new download danger type for files blocked for that reason so that we can, in future CLs, add UX specific to those files. It also generates this danger type when appropriate, but uses the generic blocking UX. Bug: 1060853 Change-Id: I6a670664d766bed860625cabcbd0d0e9a142e38e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101294 Commit-Queue: Daniel Rubery <drubery@chromium.org> Reviewed-by:
Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#750276}
-
Oksana Zhuravlova authored
TBR=jbudorick@chromium.org Bug: 1061539 No-try: true Change-Id: I4039c07fb0e14ad1dd755cdf55576c1ffe591b97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102763Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#750275}
-
S. Ganesh authored
IUpdater::UpdateAll now takes an IUpdaterObserver interface that it will eventually use to sink events. Bug: 1053729 Change-Id: I2a2a9813e2b33c4496b286329084b0e21478ba9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101934 Commit-Queue: S. Ganesh <ganesh@chromium.org> Auto-Submit: S. Ganesh <ganesh@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#750274}
-
Mario Sanchez Prada authored
This CL starts converts the message that notifies the browser process about renderer accessibility events, as well as the ACK response sent back to the renderer process once the original message is handled. Bug: 1010831 Change-Id: I435a29c176cb029cf3e419e0a4934b6c65554c84 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050316 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#750273}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/4d806b9daa24..41b7ff99df43 git log 4d806b9daa24..41b7ff99df43 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 kayce@google.com Update the What's New UI for Chrome 82 2020-03-13 tvanderlippe@chromium.org Add tooltips to extra network panel settings Created with: gclient setdep -r src/third_party/devtools-frontend/src@41b7ff99df43 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/+/master/autoroll/README.md Bug: chromium:986998 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I77af6bf98cf80abed1c130fe92d7322b550096a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103037Reviewed-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@{#750272}
-
Adithya Srinivasan authored
Adds a PORTAL_ACTIVATED generated event and handles it on Mac by dispatching the load complete notification which ensures the page gets focus (and VoiceOver also navigates through all the elements on the page, similar to what happens after a regular navigation). Bug: 1057804, 1045608 Change-Id: I2ca343e141c1011a862dd0f5bccd9b329e8f8498 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050603 Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#750271}
-