- 11 Jan, 2019 40 commits
-
-
mark a. foltz authored
The Cloud MRP does not support casting to cloud sinks from incognito. This patch filters them from the Cast dialog. Other fixes: - Use base::EraseIf consistently - Replace Equals() with == in MediaSinkWithCastModes - Misc IWYU Internal bug: b/37546693 Bug: 921094 Change-Id: I1ba7bf52e37f67ed4f6b6df3579ae109932db615 Reviewed-on: https://chromium-review.googlesource.com/c/1406309Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Commit-Queue: mark a. foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/master@{#622174}
-
Andrew Grieve authored
Noticed that the expectations were failing for no-op builds because of this. Bug: 882524 Change-Id: If0297c5e0ae0db61529089b6afbaaa430fa1ee01 Reviewed-on: https://chromium-review.googlesource.com/c/1407597 Commit-Queue: agrieve <agrieve@chromium.org> Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Cr-Commit-Position: refs/heads/master@{#622173}
-
rbpotter authored
Prefetch capabilities for recent destinations. This will speed up selection of these destinations and set up for adding a dropdown. Bug: 920056 Change-Id: I2e53a8d353b91905dc1bec49f61815a4c416f052 Reviewed-on: https://chromium-review.googlesource.com/c/1404489 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#622172}
-
Sammie Quon authored
Issue was: 1) Open two windows in clamshell, minimize both. 2) Enter tablet. 3) Activate both windows, second window will be a black screen. It seems minimizing in clamshell mode sets opacity to 0. So force opacity to 1 before activate to ensure visiblity. Test: manual Bug: 920463 Change-Id: I3858ca4ac771d23879678f8705b73a281df0b8ac Reviewed-on: https://chromium-review.googlesource.com/c/1406243Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#622171}
-
Krishna Govind authored
R=benmason@chromium.org Change-Id: Ief68f7af036fe2752cb4cdfae9a312f71dc2244a Reviewed-on: https://chromium-review.googlesource.com/c/1407384Reviewed-by:
Krishna Govind <govind@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#622170}
-
Rintaro Kuroiwa authored
- If the video config is encrypted, look for D3D11_DECODER_ENCRYPTION_HW_CENC. - It used to find a decoder config and set it to guidConfigBitstreamEncryption, but this isn't correct. There are other fields in D3D11_VIDEO_DECODER_CONFIG that is specific to the config. Change-Id: I26879eb9282a8be05fd6f579d77ea52311e62733 Reviewed-on: https://chromium-review.googlesource.com/c/1405877Reviewed-by:
Frank Liberato <liberato@chromium.org> Commit-Queue: Rintaro Kuroiwa <rkuroiwa@chromium.org> Cr-Commit-Position: refs/heads/master@{#622169}
-
Zhenyao Mo authored
This reverts commit 5ad4e08d. Reason for revert: crbug.com/918461 Original change's description: > Fix app window titlebar blending with direct composition > > Clear the DWM frame area on WM_ERASEBKGND so that Chrome's client area > blends with DWM frame for app windows. Refactor the code to update and > clear DWM frame and move it to hwnd message handler so that browser and > app windows can share the same code. > > This mimics existing logic for updating the DWM frame and adds the clear > DWM frame behavior to app windows, but one notable change is that it > will clear on every WM_ERASEBKGND message, and not just the first one. > This shouldn't have a performance impact and seems more correct anyway. > > Bug: 904322 > Change-Id: I70c3ae97a94114dd63110736a35cef4dd887b1aa > Reviewed-on: https://chromium-review.googlesource.com/c/1382928 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Bret Sepulveda <bsep@chromium.org> > Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> > Cr-Commit-Position: refs/heads/master@{#618684} TBR=sky@chromium.org,sunnyps@chromium.org,bsep@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 904322,918461 Change-Id: I681f37f264884cdfab7425eadfbd6c26bbf2d953 Reviewed-on: https://chromium-review.googlesource.com/c/1407602 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#622168}
-
Dominik Röttsches authored
Fixes situations in which a locally unique font name match masks a result for a family name match. This cannot be tested before src: local() matching is enabled by switching the flag. A layout test covering this situation will be added when the flag is enabled. Bug: 921029 Change-Id: I4123cb70aa65cb59e4a00c3a58e312ef6fa24b64 Reviewed-on: https://chromium-review.googlesource.com/c/1407069 Commit-Queue: Dominik Röttsches <drott@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#622167}
-
Thomas Guilbert authored
Returning a DecryptingRenderer from the MojoRendererFactory introduced some regressions: - DecryptingRenderer crashes when used with URL media resources. - MediaPlayerRendererClient sets up a delayed crash due to a static_cast into MojoRenderer*. This CL moves the creation of DecryptingRenderer into its own factory. The DecryptingRendererFactory is a small wrapper around MojoRendererFactory. This gets rid of both regressions, and makes it explicit where/when DecryptingRenderers are used. Bug: 919494, 919819 Change-Id: I52a091a13dd858ccb787e17fe1abacbb32ec3916 Reviewed-on: https://chromium-review.googlesource.com/c/1405814 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#622166}
-
Lukasz Anforowicz authored
Bug: 918060 Change-Id: I7ca3963e34741cb4b9d0ebb6b5f7fe8e77160000 Reviewed-on: https://chromium-review.googlesource.com/c/1399566Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#622165}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/a24a725f7834..6eeb1d2fc794 git log a24a725f7834..6eeb1d2fc794 --date=short --no-merges --format='%ad %ae %s' 2019-01-11 benjhayden@chromium.org Remove support for legacy json formats from render_histograms_viewer. Created with: gclient setdep -r src/third_party/catapult@6eeb1d2fc794 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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=sullivan@chromium.org Change-Id: Ief4b1d76a0bfd24a017020b12440496c4fbec61c Reviewed-on: https://chromium-review.googlesource.com/c/1407103Reviewed-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@{#622164}
-
Dmitry Gozman authored
When running in Incognito mode, browser()->profile() refers to the regular profile, not incognito. GetProfile() is always correct, so use that. Bug: none Change-Id: I42fbe60d923cebfd63d8274b2c779e0d5f62ca5a Reviewed-on: https://chromium-review.googlesource.com/c/1407175Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#622163}
-
Akihiro Ota authored
Adds new hotkey for ChromeVox users to quickly get battery status. This change involves: 1. Plumbing hotkey request from ChromeVox extension to ash, where battery status can be retrieved. 2. Setting up callbacks from ash to Browser and and from Browser to ChromeVox so that battery status can be reported to the user. Change-Id: I9c2b96a49a54d152bffc1e373eec352d0a902403 Reviewed-on: https://chromium-review.googlesource.com/c/1388176 Commit-Queue: Akihiro Ota <akihiroota@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Reviewed-by:
Katie Dektar <katie@chromium.org> Cr-Commit-Position: refs/heads/master@{#622162}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/4f3f4e172145..ff74da7996b9 git log 4f3f4e172145..ff74da7996b9 --date=short --no-merges --format='%ad %ae %s' 2019-01-11 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@ff74da7996b9 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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=chrome-os-gardeners@chromium.org Change-Id: Idc1070de1bb1623d5f99594edd5c5cad8974bc5a Reviewed-on: https://chromium-review.googlesource.com/c/1407548Reviewed-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@{#622161}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/6daa05d3185a..c88711f119ee git log 6daa05d3185a..c88711f119ee --date=short --no-merges --format='%ad %ae %s' 2019-01-11 lalitm@google.com trace_processor: fix argument order for lmk name id 2019-01-11 eseckler@google.com Merge "trace writer: Add a proxying StartupTraceWriter." 2019-01-11 lalitm@google.com Merge "trace_processor: fix parsing of kernel LMK events" Created with: gclient setdep -r src/third_party/perfetto@c88711f119ee The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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:122721587 TBR=perfetto-bugs@google.com Change-Id: I4fe8be1fe4210245de0761a4e6ef61775582ccfe Reviewed-on: https://chromium-review.googlesource.com/c/1407107Reviewed-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@{#622160}
-
liberato@chromium.org authored
Since ExtraTrees seem to be more useful than RandomForest for our application, remove RF in favor of them. Change-Id: Ia7301725aa55032bc7fded74139cf143f76f82f2 Reviewed-on: https://chromium-review.googlesource.com/c/1407605Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#622159}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/92ee1f9f3032..a3b64e867d2a git log 92ee1f9f3032..a3b64e867d2a --date=short --no-merges --format='%ad %ae %s' 2019-01-11 jmadill@chromium.org Fix skip for InterleavedAttributeDataBenchmark on GL. Created with: gclient setdep -r src/third_party/angle@a3b64e867d2a 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:921004 TBR=ynovikov@chromium.org Change-Id: I16edab1b06bc98217739db64a9dd867dd2addce3 Reviewed-on: https://chromium-review.googlesource.com/c/1407102Reviewed-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@{#622158}
-
Ted Meyer authored
Bug: 663999 Change-Id: Ib83d981bbb6cefa3de9f3af0ea50c2a99b8d6876 Reviewed-on: https://chromium-review.googlesource.com/c/1406149Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Cr-Commit-Position: refs/heads/master@{#622157}
-
Andrew Grieve authored
* Removes obsolete command-line flags. * Moves resource_sizes.py diff as well as failing size checks inline Bug: 914654 Change-Id: I444da444a2bbed4a154ce1d4a64bb99549e81e86 Reviewed-on: https://chromium-review.googlesource.com/c/1407375Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#622156}
-
Natalie Chouinard authored
Necessary due to ~30kB binary size increase that resulted from the addition of 3 new leveldb_proto::ProtoDatabase instances in UsageStatsDatabase. Bug: 921112 Change-Id: Ie5ad871449260c92ce08fe92bfde65273eb31218 Reviewed-on: https://chromium-review.googlesource.com/c/1407432 Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Cr-Commit-Position: refs/heads/master@{#622155}
-
Tibor Goldschwendt authored
On smartphone VR, close Chrome and show failure notification. On standalones, show FRE in 2D-in-VR mode. TBR=mthiesse@chromium.org Bug: 918915 Change-Id: I205b727b4dd1fd8f609d6c945a4711bd73f23ea4 Reviewed-on: https://chromium-review.googlesource.com/c/1406020 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#622154}
-
Nigel Tao authored
This is a reland of 7cd680d6 It is combined with the fix in http://crrev.com/c/1406488 "Fix switch on apps::mojom::LaunchSource", which was not submitted, but has some discussion of the build breakage. Original change's description: > First draft of an App Service ARC++ publisher > > Lots of TODOs, but there's enough implemented so that running "chrome > --enable-features=AppService" will populate the launcher with ARC++ > apps' names and icons, and clicking on the icon will launch the app. > > BUG=826982 > > Change-Id: Ie61b33ce9fa0588e53615f5e086d558fe6abf840 > Reviewed-on: https://chromium-review.googlesource.com/c/1377485 > Commit-Queue: Nigel Tao <nigeltao@chromium.org> > Reviewed-by: Dominick Ng <dominickn@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#621923} Bug: 826982 Change-Id: I76b5fdcc85f9992ad684c3eca57e0213050ef186 Reviewed-on: https://chromium-review.googlesource.com/c/1406490Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Nigel Tao <nigeltao@chromium.org> Cr-Commit-Position: refs/heads/master@{#622153}
-
Andrew Grieve authored
Change-Id: I20ff5e3c9e7fbf5b8a7403fce4dbd2baebd05be4 Reviewed-on: https://chromium-review.googlesource.com/c/1405722Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#622152}
-
Mike Dougherty authored
These tests have passed the last ten runs. Bug: 817810 Change-Id: I1aaee05a28878065a0ea1a4ccceaed17ec6340cd Reviewed-on: https://chromium-review.googlesource.com/c/1407591Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#622151}
-
Dominic Mazzoni authored
Previously a text field's placeholder was exposed as the hint in many circumstances, but a field that had aria-describedby would override the placeholder. Update the logic so that the placeholder text is always included in the hint text for a node. Bug: 677147 Change-Id: I15c7cfede914db6096d88039213793ec2eaa8ad4 Reviewed-on: https://chromium-review.googlesource.com/c/1385724 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#622150}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0ef2f1153a1b..03001a297efa Created with: gclient setdep -r src-internal@03001a297efa 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: Iadc96f147e0bedf82800c1717b6835531b0bd478 Reviewed-on: https://chromium-review.googlesource.com/c/1407105Reviewed-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@{#622149}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/31a486419e27..f7854e9f3fbb git log 31a486419e27..f7854e9f3fbb --date=short --no-merges --format='%ad %ae %s' 2019-01-11 recipe-roller@chromium.org Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/depot_tools@f7854e9f3fbb The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-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=agable@chromium.org Change-Id: Id3756e00abdd4aabedb09e815e071d5e070b0363 Reviewed-on: https://chromium-review.googlesource.com/c/1407098Reviewed-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@{#622148}
-
Dmitry Gozman authored
WebNavigationBodyLoader interface (and two implementations) will be used for loading navigation response body, instead of going through WebURLLoader. This patch only contains the implementation, but does not include the usage just yet. WIP usage can be seen here: https://chromium-review.googlesource.com/c/chromium/src/+/1388212. The advantages of a separate code path for navigations: - Possible to commit navigations synchronously, instead of waiting for RawResourceClient callbacks from the loader. This is a primary motivation. - Makes it easier to Onion Soupify navigation code separately from loading code. - All navigation-related special cases can be handled directly in DocumentLoader now. - We don't need a "replay fake request" mode in loader anymore. - We stop abusing ResourceRequest/ResourceResponse for navigation information (e.g. RequestorOrigin, OriginPolicy and many more). Disadvantages: - Two URLLoaderClient and body pipe consumer implementations to maintain. - Future loading features might have to touch navigation body loader as well. Although most of the navigation-related features currently have to touch navigation url request in the browser, there is a small chance that NavigationBodyLoader will be affected as well. Larger cleanups possible after this: - Remove ResourceType::kMainResource and any code related to it. - Remove ResourceRequest::GetFrameType and any code related to it. Ideally, NavigationBodyLoader could be implemented directly in Blink, but there are some dependencies on resource load statistics in content. Also, Blink is not quite ready to talk to Network Service directly. This patch corresponds to step 6.g of the doc linked in the bug. Bug: 855189 Change-Id: I3ac7b33db60e7b50e583e2006dd194c4bf843921 Reviewed-on: https://chromium-review.googlesource.com/c/1399052 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#622147}
-
Quan Nguyen authored
Bug: 912658 Change-Id: Ib56d677c3ffe5487b7861d0e4a032babd0c4d44d Reviewed-on: https://chromium-review.googlesource.com/c/1401609 Commit-Queue: Quan Nguyen <qnnguyen@chromium.org> Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#622146}
-
Mike West authored
As of [1], we've split the single `Sec-Metadata` header into multiple headers: `Sec-Fetch-Dest`, `Sec-Fetch-Site`, and `Sec-Fetch-User`. This patch does that work in Chromium. The spec change also added `Sec-Fetch-Mode`, but this patch does not. We'll add that functionality to Chromium in a future CL. Test changes pulled from clap@'s excellent PR at https://github.com/web-platform-tests/wpt/pull/14771 The test failures are expected: redirect failures are https://crbug.com/872285, object/embed failures are https://crbug.com/860510. XSLT failures are WontFix (some engines support cross-origin XSLT; Blink does not). [1]: https://github.com/mikewest/sec-metadata/commit/105103d775141912261dd164b16bd59b22f6d853 Bug: 843478 Change-Id: I7654d5e823ad813682ac3eb244bbc244a322e6ca Reviewed-on: https://chromium-review.googlesource.com/c/1402448 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#622145}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/9716603f9736..a8ea53e160f2 git log 9716603f9736..a8ea53e160f2 --date=short --no-merges --format='%ad %ae %s' 2019-01-11 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2019-01-11 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 24e71928441e..f04b56fb041f (1 commits) 2019-01-11 jvanverth@google.com Reland "Add target SkColorSpace to SkImage_GpuYUVA." 2019-01-11 ethannicholas@google.com added PLS support to SkSL 2019-01-11 halcanary@google.com fix up disabled bench: PDFBigDocBench Created with: gclient setdep -r src/third_party/skia@a8ea53e160f2 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=bsalomon@chromium.org Change-Id: Iec31fb76f4143bcb51ee62492fc4b6de27bf13a0 Reviewed-on: https://chromium-review.googlesource.com/c/1407104Reviewed-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@{#622144}
-
Andrew Grieve authored
ConcurrentHashMap has a bug on L. Also adds a checkstyle check to prevent future uses. Bug: 905903 Change-Id: Ic6afed17b5d7d3c6a150935117fb33e0408955e4 Reviewed-on: https://chromium-review.googlesource.com/c/1407493Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#622143}
-
Kevin McNee authored
HitTestAsyncQueriedDebugRegion is currently defined in an anonymous namespace in hit_test_manager.h, so each translation unit gets a seperate definition of it with internal linkage. I presume the intent here was to have HitTestAsyncQueriedDebugRegion be private to HitTestManager, so we now define it accordingly. Bug: None Change-Id: Ic546f42f6808ae25ed7f948677e6304c04ef43ec Reviewed-on: https://chromium-review.googlesource.com/c/1405698Reviewed-by:
Ria Jiang <riajiang@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#622142}
-
Renjie authored
Change-Id: Ide9efc469c6ec80c18b864579015a1dae9f75c9b Reviewed-on: https://chromium-review.googlesource.com/c/1384987Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Commit-Queue: Renjie Tang <renjietang@chromium.org> Cr-Commit-Position: refs/heads/master@{#622141}
-
Victor Vasiliev authored
Merge internal change: 228810977 R=rch@chromium.org Change-Id: Iaa05eb7fe97ea0c3d326c8530d52be8a2a7573cd Reviewed-on: https://chromium-review.googlesource.com/c/1406162Reviewed-by:
Ryan Hamilton <rch@chromium.org> Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Cr-Commit-Position: refs/heads/master@{#622140}
-
Ben Wagner authored
https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/d01e28f41f88..1e7a8f30c231 $ git log d01e28f41..1e7a8f30c --date=short --no-merges --format='%ad %ae %s' 2019-01-08 apodtele [psaux, type1] Align tracing. 2019-01-08 chris.liddell [psaux] Fix closepath (#55414). 2018-12-30 ramakrishnan.nikhil Minor documentation fix. 2018-12-29 wl * src/autofit/aflatin2.c: Some fixes from `aflatin.c' (#55310). 2018-12-26 mpsuzuki * builds/mac/README: Fix a hyperlink to defunct www.gyve.org. 2018-12-25 wl Fix links (mostly http -> https). 2018-12-25 wl * src/psaux/cffdecode.c (cff_operaor_seac): Fix numeric overflow. 2018-12-12 wl [gxvalid] Fix compiler warnings. 2018-12-12 wl Fix documentation of TrueType bytecode interpreter debug hook. 2018-12-12 wl Minor documentation fixes. 2018-12-11 wl * src/truetype/ttgload.c (TT_Hint_Glyph): Remove useless test. 2018-12-10 wl Minor documentation updates and fixes. Created with: roll-dep src/third_party/freetype/src R=bungeman@chromium.org,drott@chromium.org CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_msan_rel_ng PDFium-Roll: https://pdfium-review.googlesource.com/c/pdfium/+/48170 Change-Id: Ia3c02f363acbe30785ec27c5123fd8bf6ffd1279 Reviewed-on: https://chromium-review.googlesource.com/c/1407039Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#622139}
-
Chase Phillips authored
An upcoming change will use CreateAllBlobs() from outside the callbacks interface. Bug: 717812 Change-Id: I8292e0e7471c00d89fc7df5392e9a0a4dcd33173 Reviewed-on: https://chromium-review.googlesource.com/c/1399501 Commit-Queue: Chase Phillips <cmp@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#622138}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/ef92f656a86e..caf2cd67df84 git log ef92f656a86e..caf2cd67df84 --date=short --no-merges --format='%ad %ae %s' 2019-01-11 thestig@chromium.org Remove a NOTREACHED() in CPDF_Font::GetAdobeCharName(). Created with: gclient setdep -r src/third_party/pdfium@caf2cd67df84 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:920636 TBR=dsinclair@chromium.org Change-Id: I3f07671a4a213fa1d50c7b6d5f568a53d57db0a7 Reviewed-on: https://chromium-review.googlesource.com/c/1407100Reviewed-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@{#622137}
-
Siddhartha authored
Refactor Stack unwinder code to use a class instead of various functions with lot of arguments. Functional changes for case of current thread unwind, which is never used. 1. Handling of nullptr for the case of TraceStack for current thread api. This function called TraceStackWithContext with stack_segment_base=0, which is wrong and unwind will fail. So, set a maximum limit on stack size for unwind. 2. If stack was never copied (trace stack for current thread), then do not replace registers with 0 offset. Change-Id: I1ee96e05dcba4c658398b29e1caec96b4d733bb1 Reviewed-on: https://chromium-review.googlesource.com/c/1404262 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#622136}
-
Aaron Leventhal authored
Bug: None Change-Id: Ica82adbc7dbb37a00ce0a2b603e2d720edb6d015 Reviewed-on: https://chromium-review.googlesource.com/c/1403520Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#622135}
-