- 02 Feb, 2019 40 commits
-
-
sangwoo.ko authored
This CL allows us to use mouse with horizontal scroll function, such as tilting wheel or separate wheel for h-scroll. Bug: 2384 Change-Id: I770c629bb2391343ce66a398e4d73ad69dde569e Reviewed-on: https://chromium-review.googlesource.com/c/1414537 Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#628588}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d19ffe4b3697..559b5cf1176f Created with: gclient setdep -r src-internal@559b5cf1176f The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I702a82378065eeb874ff24522be30bb3e7fa0335 Reviewed-on: https://chromium-review.googlesource.com/c/1450976Reviewed-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@{#628587}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/72c687807f5e..48913465db5f git log 72c687807f5e..48913465db5f --date=short --no-merges --format='%ad %ae %s' 2019-02-02 reed@google.com Revert "remove legacy forward declares" 2019-02-02 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset 2019-02-02 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 10b73e92..c5cbca79 (339 commits) 2019-02-02 fmalita@chromium.org [skottie] Initial repeater support 2019-02-02 reed@google.com remove legacy forward declares Created with: gclient setdep -r src/third_party/skia@48913465db5f The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=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 TBR=borenet@chromium.org Change-Id: I0bba1e3fee6f0f72c105e357457fc1f99d8fe5d0 Reviewed-on: https://chromium-review.googlesource.com/c/1450978Reviewed-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@{#628586}
-
Henrik Boström authored
This allows us to construct the RTCError. Changing error types thrown by various methods will be done in separate CLs. Intent to Implement & Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TsJA1XX7mTE Bug: 821806 Change-Id: I876bb1b7859e69018ba970b528e515313b068c39 Reviewed-on: https://chromium-review.googlesource.com/c/1421797 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Marina Ciocea <marinaciocea@chromium.org> Reviewed-by:
Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#628585}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/fc477b3f..1603aca7 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ia3c9d863eebd46ffa6b47553ca3166cd7de29e43 Reviewed-on: https://chromium-review.googlesource.com/c/1450972Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#628584}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: I4707210ffcb5260cf351d3e65c18aeab13c4779e Reviewed-on: https://chromium-review.googlesource.com/c/1450908Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/3d6e3004f037..52d861bd49cc git log 3d6e3004f037..52d861bd49cc --date=short --no-merges --format='%ad %ae %s' 2019-02-02 syoussefi@chromium.org Disable -Wextra-semi-stmt Created with: gclient setdep -r src/third_party/angle@52d861bd49cc The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=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=cwallez@chromium.org Change-Id: Iee1f603e69c7100ad9e8392c892eab51b75d5356 Reviewed-on: https://chromium-review.googlesource.com/c/1450909Reviewed-by:
-
Chris Lu authored
Creates an instance of FindInPageManager for every WebState. Bug: 919685 Change-Id: I17f3fe7f10268c586e7aca2dbe1f0a5e3d65cc8f Reviewed-on: https://chromium-review.googlesource.com/c/1450624 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#628581}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/2205f634..fc477b3f Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I0a13c65848666ec05cf9b4fecbe70d7fc6fb1554 Reviewed-on: https://chromium-review.googlesource.com/c/1450746Reviewed-by:
-
edchin authored
This CL fixes two bugs in the page restoration placeholder: 1) The alpha of the placeholder was not previously being reset to 1.0. 2) The page restoration placeholder was only being shown at the start of a navigation. This means that the user will open a tab, it will momentarily show blank (since the page has not yet been restored) before showing the black/white placeholder. Now the black/white page will show immediately as the user enters the tab. Bug: 927843 Change-Id: If8ad4c60e05c84a240182316484e2657d46efaf0 Reviewed-on: https://chromium-review.googlesource.com/c/1450438 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3eadf1fd9424..d19ffe4b3697 Created with: gclient setdep -r src-internal@d19ffe4b3697 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I73f1fbea74b93bb080cb0992154d79a608eee1ee Reviewed-on: https://chromium-review.googlesource.com/c/1450900Reviewed-by:
-
Alex Moshchuk authored
When a new proxy is created, its renderer-side loading state is currently initialized as not loading. This is not always accurate, however, if the proxy is created for a frame that hasn't yet finished loading after a navigation. Our current DidStartLoading and DidStopLoading IPC only update the loading state of any existing proxies, but this isn't done for new proxies. Password manager is currently running into an issue stemming for the fact that a proxy's loading state is inaccurate. To fix this, this CL sends a separate IPC to update the proxy's renderer-side loading state whenever a new proxy is created for a frame that's currently loading. Bug: 916137 Change-Id: I872009c3d87df4021295e094da9b70ee69c03289 Reviewed-on: https://chromium-review.googlesource.com/c/1440728 Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#628577}
-
Ian Kilpatrick authored
This change does two things: - When reusing a cached layout result, we now don't check the subtree for a paint invalidation. Instead it appears we only need this if we have a clip property, and the visual rect on an arbitrary ancestor may change. - Within ng_paint_fragment only force paint invalidations on non-box fragment children, and when the geometry has changed. All the invalidation updates seem strictly better, we now aren't invalidating thing like floats which don't move / no geom change, etc. Bug: 636993 Change-Id: I4679a0a7bbc39f7a85a17dba35d18e89acf2f1e4 Reviewed-on: https://chromium-review.googlesource.com/c/1445908 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#628576}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=abdulsyed@chromiue.org Change-Id: Ie046a660654a908ffa4d739902c66886a65e8fa7 Reviewed-on: https://chromium-review.googlesource.com/c/1450877Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#628575}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/12eacc8a19cf..520d5f22d188 git log 12eacc8a19cf..520d5f22d188 --date=short --no-merges --format='%ad %ae %s' 2019-02-02 thestig@chromium.org Get rid of |CXFA_TextLayout::m_Blocks| wrappers. 2019-02-02 thestig@chromium.org Use a struct for |CXFA_TextLayout::m_Blocks|. 2019-02-02 thestig@chromium.org Wrap direct access to elements in |CXFA_TextLayout::m_Blocks|. 2019-02-02 thestig@chromium.org Fix indexing confusion in CXFA_TextLayout::Layout(). 2019-02-02 thestig@chromium.org Add constants for type-specific annotation form flags. 2019-02-02 thestig@chromium.org Add constants for annotation flags. 2019-02-02 thestig@chromium.org Clean up CPVT_GenerateAP. 2019-02-02 thestig@chromium.org Change |CPDF_Annot::m_pPopupAnnot| to UnownedPtr. 2019-02-02 thestig@chromium.org Add a few more constants from PDF 1.7 spec, table 8.15. 2019-02-02 thestig@chromium.org Use annotation constants in CPDF_AnnotList. 2019-02-02 thestig@chromium.org Use annotation constants in more places. 2019-02-02 thestig@chromium.org Use a struct for |CXFA_LoaderContext::blockHeights|. Created with: gclient setdep -r src/third_party/pdfium@520d5f22d188 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: I3d674c5c9926a5332bfda377ec8cd2bcc8fd3f3f Reviewed-on: https://chromium-review.googlesource.com/c/1450897Reviewed-by:
-
Marijn Kruisselbrink authored
This is the first step towards merging DispatcherHost into BackendImpl. Bug: none Change-Id: If0a387b71968823cd50dfff628f758ef6fc01e63 Reviewed-on: https://chromium-review.googlesource.com/c/1450752 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#628573}
-
rbpotter authored
Polymer 2 is currently on by default on all platforms except for Chrome OS. The automated tests are now all passing with Polymer 2 on Chrome OS, with the exception of OOBE/Login related tests. This CL turns on Polymer 2 by default on Chrome OS except for the OOBE page, so that Web UI pages using Polymer can be tested to see if there are any additional issues that have not been detected by the tests. See https://crrev.com/c/1414590 for the addition of the WebUIPolymer2Exceptions flag, which ensures that Polymer 1 will still be used for the OOBE page after this CL lands. Bug: 738611 Change-Id: Ic103a94f2b1e2283596daa9b54ac2d60aa210ba4 Reviewed-on: https://chromium-review.googlesource.com/c/1447026 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#628572}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/dbb1fe52480b..72c687807f5e git log dbb1fe52480b..72c687807f5e --date=short --no-merges --format='%ad %ae %s' 2019-02-02 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader debaacab10b5..cd610c9a9dbc (1 commits) 2019-02-01 robertphillips@google.com Revert "Add isTextureable parameter to GrContextThreadSafeProxy::createCharacterization" Created with: gclient setdep -r src/third_party/skia@72c687807f5e The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=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 TBR=borenet@chromium.org Change-Id: Ie1cfd27cb459ab235ef553cbd25a78967d2a0b2e Reviewed-on: https://chromium-review.googlesource.com/c/1450747Reviewed-by:
-
Jinho Bang authored
Before this patch, when calling updateWith() w/o shippingOptions in PaymentRequestUpdateEvent, it will be set to empty array by force. This is a implementation bug and doesn't match behavior with the spec[1]. It cause that calling updateWith() with no shippingOptions resets the shipping address on payment sheet UI. To resolve the problem, this patch makes the shippingOptions member optional. FYI, we already fixed it for payerdetailchange and paymentmethodchange events[2]. Use count data: https://www.chromestatus.com/metrics/feature/timeline/popularity/2622 https://www.chromestatus.com/metrics/feature/timeline/popularity/2623 [1] https://w3c.github.io/payment-request/#update-a-paymentrequest-s-details-algorithm [2] https://chromium-review.googlesource.com/c/chromium/src/+/1280563 Bug: 902291 Change-Id: If7b2ba6890ac4905ad1acf79c034fe866ec3beb4 Reviewed-on: https://chromium-review.googlesource.com/c/1438980Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Jinho Bang <jinho.bang@samsung.com> Cr-Commit-Position: refs/heads/master@{#628570}
-
Alexei Filippov authored
The mode can be controlled with --memlog-in-process flag or via the Finch experiment. In-process mode does also imply samples collected on the client side (non-streaming mode). BUG=923459 Change-Id: Ic1866231ac2ad4cbdf03e8664c2871ab22e12931 Reviewed-on: https://chromium-review.googlesource.com/c/1435757 Commit-Queue: Alexei Filippov <alph@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#628569}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/457442a6956e..3eadf1fd9424 Created with: gclient setdep -r src-internal@3eadf1fd9424 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:123422976 TBR=mmoss@chromium.org Change-Id: I8aaab3eeac0da9f8aed19868d06db569d3f5815e Reviewed-on: https://chromium-review.googlesource.com/c/1450892Reviewed-by:
-
edchin authored
Adding myself since I've fixed a number of side swipe bugs and we should have at least two owners per folder. Change-Id: I7c1ace9bb9d5c76778fe7be2293895af7f4347c4 Reviewed-on: https://chromium-review.googlesource.com/c/1450898Reviewed-by:
Justin Cohen <justincohen@chromium.org> Auto-Submit: edchin <edchin@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#628567}
-
Vikas Soni authored
Refactor CodecImage, ImageReader and SurfaceTexture to make it usable by SharedImage code in future. Added a bool parameter to hint if SurfaceTexture/ImageReader should bind egl images to the texture target or not. Bug: 900963 Change-Id: I4630d4432a850427b029b9f05460b0e7e2459a3f Reviewed-on: https://chromium-review.googlesource.com/c/1447013 Commit-Queue: vikas soni <vikassoni@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#628566}
-
Brian White authored
Bug: 923083 Change-Id: Ifc3bc99cff07100930607574e786194989a5a43b Reviewed-on: https://chromium-review.googlesource.com/c/1450292 Commit-Queue: Brian White <bcwhite@chromium.org> Auto-Submit: Brian White <bcwhite@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#628565}
-
Ting Shao authored
If ServiceWorkerImportedScriptUpdateCheck is enabled, there are two phases in updating: byte-to-byte checking and launching a new service worker for install/activate events. In the second phase, we need to make a copy of scripts which were identical during byte-to-byte checking instead of download the scripts from the network in order to avoid issuing the network request for the scripts more than twice. This patch checks the compared script info generated in the script byte-to-byte update check and decides whether a copy is needed. ServiceWorkerCacheWriter is extended to support copy only operation. After copy is done, ServiceWorkerInstalledScriptLoader is created to load the new copy. Bug: 648295 Change-Id: I1886cea0eb9511dedc4548fc3ac81d5306b27051 Reviewed-on: https://chromium-review.googlesource.com/c/1424601 Commit-Queue: Ting Shao <ting.shao@intel.com> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#628564}
-
Zhenyao Mo authored
We add a trace event when we present the video swapchain. These events includes presentation mode and pixel format. Based on existence of such events and their params, we can decide if the expected video frame presentation happened. Note that we found out that GetFrameStatisticsMedia is flaky and this is out of our control. So if a test fails because of this, we repeat it a couple times. BUG=867136 TEST=GPU bots R=kbr@chromium.org,piman@chromium.org,sunnyps@chromium.org Change-Id: I1f0972f2887a72ad46f533edda274ffc7608790b Reviewed-on: https://chromium-review.googlesource.com/c/1441374Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#628563}
-
Tommy Steimel authored
This reverts commit 88e66b00. Reason for revert: causing compilation error on WebKit Linux Trusty MSAN: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Linux%20Trusty%20MSAN/12526 Original change's description: > Add dav1d decoder and build configurations. > > We're planning to experiment with av1 decoders, so this change > adds support for dav1d in Chromium. > > This sets up the dav1d repo per modern 3rd party style: It's a > read-only clone of dav1d's GitHub mirror with the build config > and helper scripts living in the main Chromium src.git repo. > Due to this configuration, no local patches can be made. > > Two helper scripts have been added "generate_configs.py" and > "generate_source.py". The former requires a few dependencies > spelled out in the README.chromium. The latter works simply > by globbing some source patterns into GN variables. > > Thus far it seems all posix configurations (mac, linux, CrOS) > can share the same config, so only support linux and windows > in x86, x64 configurations has been added. > > ARM support is not enabled yet since we haven't enabled libaom > for ARM and similarly dav1d is lacking much of the SIMD code. > > To wire everything up this also: > - Adds a media::VideoDecoder based implementation and unit test. > - Adds a disabled-by-default Dav1dVideoDecoder base::Feature. > > Bug: 924370 > Change-Id: I64ef6cdf442d55f43c1782ee22289e5a2305d9bd > Reviewed-on: https://chromium-review.googlesource.com/c/1303406 > Commit-Queue: Dale Curtis <dalecurtis@chromium.org> > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Reviewed-by: Frank Liberato <liberato@chromium.org> > Reviewed-by: Max Moroz <mmoroz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#628557} TBR=dalecurtis@chromium.org,jam@chromium.org,liberato@chromium.org,mmoroz@chromium.org,dominic@google.com Change-Id: Iae8c2e93ab0dc5aff6861ddff0cbbef6d90cab93 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 924370 Reviewed-on: https://chromium-review.googlesource.com/c/1450540Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#628562}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/33cc9c60892a..12eacc8a19cf git log 33cc9c60892a..12eacc8a19cf --date=short --no-merges --format='%ad %ae %s' 2019-02-02 tsepez@chromium.org Copy m_NewAddedNodes before iterating over it. Created with: gclient setdep -r src/third_party/pdfium@12eacc8a19cf The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:927644 TBR=dsinclair@chromium.org Change-Id: I2352dd7664413bc5fe985ae3221b35d2cd037b38 Reviewed-on: https://chromium-review.googlesource.com/c/1450734Reviewed-by:
-
Ken Buchanan authored
For Web Authentication we would like to determine the prevalance of BLE capabilities on clients to understand whether BLE security keys and caBLE devices are viable for those users. This re-enables the UMA on OSX to determine Bluetooth availability and capabilities, and adds similar metrics to Windows and Chrome OS. Bug: 907279 Change-Id: I8da9165bca5177cb08176cc4ce812340456a97d4 Reviewed-on: https://chromium-review.googlesource.com/c/1437721 Commit-Queue: Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#628560}
-
Stephen Barber authored
BUG=chromium:926292 TEST=none Change-Id: I7f96c258d77482c2e431cbdea508939f070da4a7 Reviewed-on: https://chromium-review.googlesource.com/c/1444191Reviewed-by:
Xiaochu Liu <xiaochu@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> Cr-Commit-Position: refs/heads/master@{#628559}
-
Jazz Xu authored
[Media Controls] Give focus back to last focused item after interact with scrollbar in overflow menu After interacting with scrollbar, the popup menu gain focus, which makes user unable to traverse option using "up" or "down" key in popup menu (They have to hover the menu again to enable it). This CL fixed the issue by switching focus back to last focused item whenever the popup menu gains focus. Bug: 922360 Change-Id: I0809ff8b0c11927814ad83615fc39729d92ad053 Reviewed-on: https://chromium-review.googlesource.com/c/1416820 Commit-Queue: Jazz Xu <jazzhsu@chromium.org> Reviewed-by:
-
Dale Curtis authored
We're planning to experiment with av1 decoders, so this change adds support for dav1d in Chromium. This sets up the dav1d repo per modern 3rd party style: It's a read-only clone of dav1d's GitHub mirror with the build config and helper scripts living in the main Chromium src.git repo. Due to this configuration, no local patches can be made. Two helper scripts have been added "generate_configs.py" and "generate_source.py". The former requires a few dependencies spelled out in the README.chromium. The latter works simply by globbing some source patterns into GN variables. Thus far it seems all posix configurations (mac, linux, CrOS) can share the same config, so only support linux and windows in x86, x64 configurations has been added. ARM support is not enabled yet since we haven't enabled libaom for ARM and similarly dav1d is lacking much of the SIMD code. To wire everything up this also: - Adds a media::VideoDecoder based implementation and unit test. - Adds a disabled-by-default Dav1dVideoDecoder base::Feature. Bug: 924370 Change-Id: I64ef6cdf442d55f43c1782ee22289e5a2305d9bd Reviewed-on: https://chromium-review.googlesource.com/c/1303406 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#628557}
-
David Black authored
Previously we used a DialogClientView which supported handling of the ESCAPE key to close the widget. Now, we're switching to the lighter weight ClientView which necessitates us adding ESCAPE support ourselves. Bug: b:123607402 Change-Id: I64c1fe1cd38f6f9daafc993956c10f143fa5a4f4 Reviewed-on: https://chromium-review.googlesource.com/c/1446405 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#628556}
-
Erik Anderson authored
The SSLUITestWithExtendedReporting.TestBrokenHTTPSReportingCloseTab test is failing on official builds because the ReportCertificateErrors sending threshold is configured to be less than 1.0 (100%) for the stable channel. This change forces it to 1.0 to ensure the test passes regardless of the value provided by the experimentation server. Bug: 795820 Change-Id: Icbcb839745be7e67d15e2ce998d943d37369e23b Reviewed-on: https://chromium-review.googlesource.com/c/1450239Reviewed-by:
Emily Stark <estark@chromium.org> Commit-Queue: Erik Anderson <Erik.Anderson@microsoft.com> Cr-Commit-Position: refs/heads/master@{#628555}
-
Wez authored
Tear-down any existing View-related resources (e.g. Aura window, focus controller etc) if a CreateView() request is received while a View is already active for this Frame. Bug: 920490 Change-Id: Iec4f7d393e33d583bc7dc8caf0bbea5f4ae11f6d Reviewed-on: https://chromium-review.googlesource.com/c/1423901 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#628554}
-
Michael Giuffrida authored
The Web style guide's JS section should link to the ES supported features doc, and vice versa, so that both are discoverable. Also gives the ES Support page a proper title: "ECMAScript Features in Chromium" Bug: None Change-Id: I4af3471a4eba1f7377826a35c08cbb8841db411d Reviewed-on: https://chromium-review.googlesource.com/c/1450586 Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b4138ddf946e..457442a6956e Created with: gclient setdep -r src-internal@457442a6956e The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:905792 TBR=mmoss@chromium.org Change-Id: Ibac5ca6902a24ba009be5632865fc16a6df96e85 Reviewed-on: https://chromium-review.googlesource.com/c/1450739Reviewed-by:
-
Amos Lim authored
Move notification_data_conversions* from content/renderer/notifications to third_party/blink/public/common and third_party/blink/common. Since notification_data_conversions converts data in blink side only, it no longer needs to be placed in content. Bug: 919396 Change-Id: I184d17abb4ea65390603870760c43b5bcc5063e1 Reviewed-on: https://chromium-review.googlesource.com/c/1447398Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Amos Lim <eui-sang.lim@samsung.com> Cr-Commit-Position: refs/heads/master@{#628551}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/91d469aae063..3d6e3004f037 git log 91d469aae063..3d6e3004f037 --date=short --no-merges --format='%ad %ae %s' 2019-02-02 ianelliott@google.com Implement EGL_ANDROID_recordable for Vulkan back-end. 2019-02-01 jonahr@google.com Fix unnecessary copy of for loop variables in ANGLE 2019-02-01 syoussefi@chromium.org Use env variable to select default backend 2019-02-01 jmadill@chromium.org Enable -Wextra-semi and -Wextra-semi-stmt. Created with: gclient setdep -r src/third_party/angle@3d6e3004f037 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=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 BUG=chromium:926235 TBR=cwallez@chromium.org Change-Id: I1e6412420ea86830b3aeca7a6be29c14fa8cab2a Reviewed-on: https://chromium-review.googlesource.com/c/1450735Reviewed-by:
-
Stephen Martinis authored
All instances are set to true, so this flag isn't really needed. Bug: 883150 Change-Id: I6313be44075003ab28801d450daacf25d6bca4b0 Reviewed-on: https://chromium-review.googlesource.com/c/1449010 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#628549}
-
