- 13 Mar, 2020 40 commits
-
-
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:
-
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:
-
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:
-
John Budorick authored
Follow up to crrev.com/c/2095448 Bug: 1060280, 1061511 Change-Id: Idf000e44348a779b0205e9cee610e359cf702e99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103132Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#750270}
-
Raymond Toy authored
The pause_cb_ Closure is a OnceClosure. Change Pause() and Flush() to take a OnceClosure. This fixes text_render.cc not to use Closure. Every instance is now either RepeatingClosure or OnceClosure. Bug: 1007799 Change-Id: I6ad66ccb149cac914325da98da2f4c0a3965fd7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095709Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#750269}
-
Maggie Chen authored
|has_hw_overlay_support_| in the DC overlay Processor is updated after display change. This cap is queried directly from direct_composition_surface_win. All the other overlay_support capabilities which are used for passing data have been removed. |use_dc_overlays_for_video| is removed from |capabilities| of gles2_cmd_decoder and gles2_cmd_decoder_passthrough. |supports_dc_video_overlays| is removed from |capabilities| of output_surface. Bug: 1042989 Change-Id: I9fcfd0a0e9e2e19db00ea0418cfd299e17664cae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068920Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
weiliangc <weiliangc@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#750268}
-
Matthew Mourgos authored
This change adds metrics, for the gesture navigation screen, which records the amount of time that each individual page is shown to the user (pages include Intro, Home, Overview, and Back). Bug: 1055690 Change-Id: Iddc76fc5f3b1666813693418b51ae943eec067fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098770Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Cr-Commit-Position: refs/heads/master@{#750267}
-
Michael Thiessen authored
Bug: 1061460 Change-Id: I5d5c585ff3cecae9ac69c12737130bda89257b11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102778Reviewed-by:
-
Hesen Zhang authored
- Defined QueryTile proto and in-memory struct. - Defined a collection_store interface. - Implemented QueryTileStore. TODO in next CLs: proto_conversion, query_tile_store_unittest, query_tile_group_manager(tree operations). Bug: 1060805c Change-Id: I6da3c9be67b34843594476ae1c1302206a19f1fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099228 Commit-Queue: Hesen Zhang <hesen@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
-
David Bokan authored
In https://crrev.com/4d25b125dae5 I changed the scroll tree parenting logic so that elements in position:fixed subtrees have the LayoutView's ScrollNode as the scroll parent. This made sense since scrolling over a fixed element should cause the document to scroll. However, this is slightly different from how the transform tree looks. Because scrolling the document doesn't cause position:fixed eement so translate, these nodes don't have the LayoutView's ScrollTranslation transform node as an ancestor. As a simple example, a scrolling document with a position:fixed <div> scroller will generate the following scroll and transform trees (approximately): *ScrollTree* *TransformTree* Root Root | | VisualViewport Translation VisualViewport | / \ LayoutView Translation / \ | Fixed LayoutView Fixed Scroller Translation The situation above makes sense for what parent-child relationships mean in each tree: the scroll tree encodes how scrolls chain; scrolling on a child should bubble up to its parent in this tree. The transform tree encodes the physical effect of scrolling a node. In the above example, scrolling from the fixed scroller should bubble up to the LayoutView (when the scroller is fully scrolled) but scrolling the LayoutView will not cause movement of the fixed scroller. The above makes sense but caused sticky code to get confused. A sticky constraint is attached to the scroll translation node. With the above situation, this meant that inside a fixed subtree, we'd attach it to the VisualViewport's scroll translation node. This was unexpected; the constraints are in "document coordinates", meaning that to translate them into the viewport space we must apply the scroll offset [1]. The compositor would use the visual viewport's (typically 0) scroll offset to adjust these values, leading to incorrect calculations. This previously worked because the scroll node used in a fixed subtree would be the visual viewport (before the CL mentioned at the top). In [2] we check whether the current overflow clip is also our scroller, prior to the CL this check have failed because "our scroller" was the visual viewport but our clip was the LayoutView. Now they are both the LayoutView. The fix in this CL is to make the check in [2] more stringent; we also want to make sure that our scroller is the nearest scroller in the transform tree. That is, if we scroll it, will we cause the current node to move? If not, we don't need a sticky constraint on the compositor because user scrolling can't change the sticky's offset relative to its clip. [1] https://cs.chromium.org/chromium/src/cc/trees/property_tree.cc?l=321&rcl=628f869d1fda631a85f051ad13b5d278319298fc [2] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/paint/paint_property_tree_builder.cc?l=553&rcl=99a5a1266f303ba6ae46174a2b4cbd165ea7e934 Bug: 1019142 Change-Id: I781943ff43514905d399803c780c6081d7d47e8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097542Reviewed-by:
Robert Flack <flackr@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750264}
-
Mustafa Camurcu authored
Extend metrics Arc.Runtime.Performance.* until 2021-03-11 TEST=None Bug: b/151314714 Change-Id: Ib07a54a2f162e8bedde7944262e146c89dcc1186 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101721 Commit-Queue: Mustafa Camurcu <camurcu@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#750263}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ef7ec269b5b5..034b5438d90f Created with: gclient setdep -r src-internal@034b5438d90f 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 jbudorick@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.chrome.try:linux-chromeos-chrome Bug: chromium:1047357 Tbr: jbudorick@google.com Change-Id: I7c6dbc2abb8e7b2a7f8c318dcaf2ea47460e1100 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103032Reviewed-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@{#750262}
-
Mustafa Camurcu authored
Extend metric Arc.PlayStoreShown.TimeDelta until 2021-03-11 TEST=None Bug: b/151314714 Change-Id: Ia5e9320858138a4e6d7f12d0d77cbf2a7f587efe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101545 Commit-Queue: Mustafa Camurcu <camurcu@chromium.org> Reviewed-by:
-
Sinan Sahin authored
Today, most parts of the code assume the browser controls min-height is 0. This causes issues with the layout size and the fullscreen mode. The most obvious issues currently are: - If a min-height is set, ChromeFullscreenManager#controlsResizeView() always returns true since the controls aren't completely hidden. - Similarly if a min-height is set, position: fixed elements are sized as if the controls are fully showing. This CL changes the "browser controls resize/shrink blink" logic to try and fix the issues listed above. With the changes in this CL, the controlsResizeView bit will be false if the controls are at the min-height. Bug: 1049301 Change-Id: Ieb95e92c983b56b42a640f726c60c2eec9964064 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2048276 Commit-Queue: Sinan Sahin <sinansahin@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750260}
-
Mustafa Camurcu authored
Extend metrics Arc.PlayAutoInstallRequest.* until 2021-03-11 Bug: b/151314714 Change-Id: Id7734c89b42aa1122762a82f76b49bd80fd3df77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101543 Commit-Queue: Mustafa Camurcu <camurcu@chromium.org> Reviewed-by:
-
Sebastien Marchand authored
This uses the Clang profiling config during the instrumentation step of a PGO build. This allows getting the profiling data out of the sandboxed processes. This is not an ideal end state, ideally the coverage configuration should be refactored and things common to the two configurations should be moved to a new base config. This requires to use the new version of goma, see go/ma-rbe-dogfood (see crbug.com/990981#c26 for more details). To build a PGInstrumented build (first step to do a PGO build) compile with the following GN args: is_component_build = false is_debug = false chrome_pgo_phase = 1 use_goma = true Bug: 1056189 Change-Id: I717efdcbb6993ad574acce4c0f91eb5fb5bf3972 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076424 Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#750258}
-
Jon Mann authored
When Wi-Fi sync is first enabled and a list of synced networks has to be merged with the local networks on a device, use the last connected timestamp to decide which configuration should be used. Bug: 966270 Change-Id: Id7688a0fdb9e7922cee8ffec0ef69b804436e3e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093274Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Jon Mann <jonmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#750257}
-
Jeff Yoon authored
The iOS tests were being run as gtests, but with the isolated merge script because of iOS' output format (standard JSON output). Moving them to use isolated_scripts instead, as it shortens the definition in test_suites.pyl, and accomplishes the same. Bug: 1055164 Change-Id: Icffb1a1cf72681e2ad08c5a3031d50e842a003f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100714Reviewed-by:
-
Mustafa Camurcu authored
Extend lifetime of Arc.IconLoadFromFileTime.* metrics until 2021-03-11 Bug: b/151314714 Change-Id: I2252633d23d8747fd6731f2d4eb3ef69709e550e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100636 Commit-Queue: Mustafa Camurcu <camurcu@chromium.org> Reviewed-by:
-
Ahmed Fakhry authored
The first ever default desk created after boot should not trigger any UMA stat reporting. The histograms are deprecated, and replaced by Ash.Desks.NewDesk2, and Ash.Desks.DesksCount2 respectively. BUG=1060709 Change-Id: I09f851009aa05a71e73e914692919d2f8150344e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095973Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#750254}
-
Mustafa Camurcu authored
Extend lifetime of Arc.FirstAppLaunchRequest.TimeDelta metric until 2021-03-11 Bug: b/151314714 Change-Id: I8308e1684468acc8aef37927d40e529ffd05249e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100948 Commit-Queue: Mustafa Camurcu <camurcu@chromium.org> Reviewed-by:
-
Jan Wilken Dörrie authored
This change modifies LeakDetectionRequest to explicitly check for HTTP_TOO_MANY_REQUESTS, indicating the user ran out of quota. It modifies corresponding enums and introduces an optional LeakDetectionError to the LookupSingleLeakCallback, so that the error can be forwarded to consumers like the Password and Safety Check. Bug: 1061108 Change-Id: I86d561b47bbf39e996a425dbd3459eb8bbda52ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100941 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#750252}
-
Lei Zhang authored
Add helper functions to do the conversion and switch to gfx equivalents. Bug: 10611824 Change-Id: Ie4633980d37ba97a92f46b8f465356a4334ac483 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101984 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#750251}
-
Xianzhu Wang authored
Bug: 524134 Change-Id: I99e53d134f2542f06d63519ad2a96b4d24738649 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101494Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#750250}
-
Nate Fischer authored
No change to production logic, only test shell. This adds 'system_webview_shell_package_name' to configure WebView shell's package name. This is handy for Android emulators, because the default package name will cause signature mismatches. I kept the original documentation (for removing the shell from the system image) because it may be relevant for some use cases. But I hope the GN arg is a simpler solution for most developers. Fixed: 1061211 Test: $OUT/bin/system_webview_shell_apk package-info (verify name) Test: $OUT/bin/system_webview_shell_apk install (succeeds on emulator) Test: Upload to gerrit > open file > click "gitiles" > verify markdown Change-Id: I24a35524bc5042da33b8203637ec67a0f610f363 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101859Reviewed-by:
Hazem Ashmawy <hazems@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#750249}
-
Natalie Chouinard authored
This is a follow up to https://crrev.com/i/2756704. Bug: 1047357 Change-Id: I850d2478e978d9dab188f9a2a0913ac30a2083c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101716 Commit-Queue: Gang Wu <gangwu@chromium.org> Auto-Submit: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#750248}
-
Sean Gilhuly authored
There are variants of viz_unittests that use SkiaRenderer Dawn if it is enabled in the build, and variants of cc_unittests are underway. Add them to the SkiaRenderer Dawn FYI bot, which builds with the gn arg "use_skia_dawn = true". Bug: 1021566 Change-Id: Ia0d96a9389308f45e4a697455f396d69d7d20db4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094758Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#750247}
-
Charlie Hu authored
This CL migrates UnsizedMedia from feature policy to document policy. Following web tests are being migrated: - unsized-media.tentative.https.sub.html - unsized-media-reporting.html Following web tests are removed, because document policy currently does not have a js API to list all features available. - feature-policy-unsized-media-disabled.html - feature-policy-unsized-media-enabled.html Bug: 993790 Change-Id: Id5e0189c0277c940177460380970eab0015109d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097028 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#750246}
-
Robbie McElrath authored
This CL moves the Java-side definition of the kGenericSensorExtraClasses Feature from ChromeFeatureList to a new DeviceFeatureList class that lives in //services/device/public/java. This will allow non-Chrome embedders to query the status of the Feature from Java. Bug: 1058597 Change-Id: Iab3c75fea6c8755de52714be7776547a774842d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095445 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#750245}
-
Oksana Zhuravlova authored
TBR=dmurph@chromium.org Bug: 1061251 No-Try: true Change-Id: I30bbc831be9069b6b246242f3ed4eeb46576e65c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103247 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
-
Aaron Leventhal authored
There is a discrepancy between BlinkAXTreeSource::GetChildren() and BlinkAXTreeSource::GetParent(). - GetChildren() does not return direct children when they are ignored and not included in the tree. This is because when AXNodeObject::InsertChild() visits an object that is ignored and not included in tree, it recurses and inserts the next generation. - GetParent() always returns the direct parent. This discrepancy an lead to confusion within AXTreeSerializer, with respect to analyzing reparenting. Bug: 651614 Change-Id: I4e4c8c6a2900cf5516cc98f3b260e619220ea7e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095882 Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Adam Ettenberger <Adam.Ettenberger@microsoft.com> Reviewed-by:
Jacques Newman <janewman@microsoft.com> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#750243}
-
