- 28 Nov, 2018 40 commits
-
-
Kent Tamura authored
Bug: 905922 Bug: https://github.com/w3c/webcomponents/issues/187 Change-Id: I979d51cdf399d78aa51b2d5692b7e93df3461410 Reviewed-on: https://chromium-review.googlesource.com/c/1353029Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#611585}
-
Maggie Chen authored
This finch experiment will enable Direct Composition overlay for software protected video on all GPUs including AMD and nVidia in Windows. Currently, Direct Composition overlay is only enabled for Intel GPUs. Bug:906722 Change-Id: If454f8b80f0c9cefe564b5aaa1da2232973c192a Reviewed-on: https://chromium-review.googlesource.com/c/1342399 Commit-Queue: Maggie Chen <magchen@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#611584}
-
Ken Rockot authored
Adds fuzzers for Channel and NodeChannel, the two main primitives over which Mojo transmits all IPC messages. Both objects define and parse different layers of the internal control protocol. The Channel fuzzer just fires random data at a platform-specific Channel implementation, covering the lowest protocol layer which parses a Channel::Message header. The NodeChannel fuzzer sends well-formed Channel::Message header data with a fuzzed payload to a NodeChannel receiver, which covers parsing the rest of the internal control protocol. Bug: 900440 Change-Id: I9fe9b88fc3bced17427db28daad931fb64a44280 Reviewed-on: https://chromium-review.googlesource.com/c/1352828 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Oliver Chang <ochang@chromium.org> Cr-Commit-Position: refs/heads/master@{#611583}
-
Joel Hockey authored
Add pkedcjkdefgpdelpbcmbmeomcjbeemfm in addition to enhhojjnijigcajfphajepfemndkmdlo Bug: 873322 Change-Id: Ic584d17466bf14dbe79122878186dedb18408d4b Reviewed-on: https://chromium-review.googlesource.com/c/1353030Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Stuart Langley <slangley@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#611582}
-
Nigel Tao authored
BUG=826982 Change-Id: I1feaec0eae9a0d2413ce4b2200da1d87b798ae98 Reviewed-on: https://chromium-review.googlesource.com/c/1352124 Commit-Queue: Nigel Tao <nigeltao@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#611581}
-
Nigel Tao authored
BUG=826982 Change-Id: I9d82c8f6d4abad6dd80c6825691075e68c749b1a Reviewed-on: https://chromium-review.googlesource.com/c/1349145 Commit-Queue: Nigel Tao <nigeltao@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#611580}
-
Nigel Tao authored
That design was introduced, some months ago (2018 July), in crrev.com/c/1127513 "Create a skeleton App Service and App Registry". The 'skeleton' App Registry wasn't actually called anywhere in production code, only in tests. Some months later (2018 November), crrev.com/c/1328626 "Add chrome/services/app_service design doc" and crrev.com/c/1338590 "Add an App Service registry implementation" gave more detail or 'flesh on the bones' about how the App Service (and the registry aspect of that service) would work. This involved a new design, also called the "App Registry". The old design was deprecated. This commit deletes that old code, removing the confusion in having both the old and new designs, both called "App Registry". The new design does not depend on the prefs service, so some dependencies were removed. In the future, some other to-be-written part of the App Service may depend on the prefs service. At that future point in time, some of these dependencies (and the 'pause incoming Mojo requests until the pref service is ready' dance in app_service.cc) may be re-introduced. But for now, YAGNI. BUG=826982 Change-Id: I4ad52c5b9ba307a3922ed6dda330b7d9aedf29a0 Reviewed-on: https://chromium-review.googlesource.com/c/1348881 Commit-Queue: Nigel Tao <nigeltao@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/59cfd3543875..0d007d7c4f11 git log 59cfd3543875..0d007d7c4f11 --date=short --no-merges --format='%ad %ae %s' 2018-11-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision aed90203..b04e513f (611312:611432) 2018-11-28 jeroendb@webrtc.org Fix raddr on srflx and relay candidates 2018-11-27 qingsi@webrtc.org Revert "Delay call to Destroy until after SignalDone has finished firing." 2018-11-27 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 81c26a09..aed90203 (611047:611312) 2018-11-27 zstein@webrtc.org Delay call to Destroy until after SignalDone has finished firing. 2018-11-27 peah@webrtc.org AEC3: Add metrics for API call jitter 2018-11-27 jakobi@webrtc.org Add PeerConnection option to configure minimum audio jitter buffer delay. 2018-11-27 artit@webrtc.org Fix webrtc-internal configs to run perf tests on separate bots 2018-11-27 terelius@webrtc.org Batch RTC event log output if using the new wire format. 2018-11-27 jakobi@webrtc.org Expose delayed packet outage as a cumulative metric of samples in the new getStats API. Created with: gclient setdep -r src/third_party/webrtc@0d007d7c4f11 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng BUG=chromium:None,chromium:905690,chromium:905542,chromium:None,chromium:905542,chromium:907234 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I956aed4c208a54a3ab6446e9ab8780d9f08669f2 Reviewed-on: https://chromium-review.googlesource.com/c/1352608Reviewed-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@{#611578}
-
chrome://flagsJinsuk Kim authored
Creates a new entry in chrome://flags for gesture navigation that will allow horizontal scroll gesture to navigate forward/backward. Bug: 865567 Change-Id: Id35d8ad261e2f4a29e34c4b4a73eed04029ba643 Reviewed-on: https://chromium-review.googlesource.com/c/1350411 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#611577}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/3b7c9d099b0d..83b2f0e8a2e0 git log 3b7c9d099b0d..83b2f0e8a2e0 --date=short --no-merges --format='%ad %ae %s' 2018-11-28 jdarpinian@chromium.org WebGL: Forbid GenerateMipmap on zero-size textures Created with: gclient setdep -r src/third_party/angle@83b2f0e8a2e0 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:898351 TBR=fjhenigman@chromium.org Change-Id: I2d031595d94047c86a380c3f2ab287def933ae5d Reviewed-on: https://chromium-review.googlesource.com/c/1351137Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8640c5d4e9f9..3a1201f66f4b Created with: gclient setdep -r src-internal@3a1201f66f4b 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: If2d920f72d276cc5a9a1843aa1d05346187068e7 Reviewed-on: https://chromium-review.googlesource.com/c/1352990Reviewed-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@{#611575}
-
Chris Hall authored
R=dmazzoni,aboxhall BUG=889370 Change-Id: I1a3ced4e63b289bd1aa2bc4fc40e28c6a2fd7e9e Reviewed-on: https://chromium-review.googlesource.com/c/1307022Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Commit-Queue: Chris Hall <chrishall@chromium.org> Cr-Commit-Position: refs/heads/master@{#611574}
-
Jinsuk Kim authored
This CL makes the ephemeral tab in peeked state 150% larger. Top portion of the content being loaded as well as the progress bar becomes quite visible. Bug: 894619 Change-Id: I2aa5d39a4a9592c07421136c00d74c54b9c916ae Reviewed-on: https://chromium-review.googlesource.com/c/1349150Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#611573}
-
Zhiqiang Zhang authored
This reverts commit 7c453583. Reason for revert: This introduces some regression in some cases. The old logic works just fine so it is safe to revert. Original change's description: > [Android MR] Postpone route selection until session launch > > Previously, we unselect and re-select the route due to CAF limitation. > The reason is that we need to set the receiver app ID after the user > choose a device. However CAF won't be able to know a device was selected > after the receiver app ID gets changed. > > In this CL, to solve the issue, we intercept the click event in > MediaRouteChooserDialog (which would select the route automatically). > The route selection is postponed right before session launch. Therefore > we are able to set the receiver app ID and select the route to get rid > of CAF limitation. > > Bug: 711860 > Change-Id: I5b1534d36d540b62199a6fb739c56ad5131c2711 > Reviewed-on: https://chromium-review.googlesource.com/c/1351893 > Reviewed-by: Thomas Guilbert <tguilbert@chromium.org> > Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#611437} TBR=zqzhang@chromium.org,tguilbert@chromium.org Change-Id: I30322daecf8c866fdda9e846d0cb37d9a319f033 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 711860 Reviewed-on: https://chromium-review.googlesource.com/c/1352973Reviewed-by:
Zhiqiang Zhang <zqzhang@chromium.org> Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org> Cr-Commit-Position: refs/heads/master@{#611572}
-
Takuto Ikuta authored
Due to too many include, v8_context_snapshot_external_references.cc has long compile time. This CL removes header files for ConstructorCallback by introducing forward declaration. That reduces compile time of v8_context_snapshot_external_references.cc from 24.6s to 4.5s in Z840 Linux. Change-Id: I247e6a92dfdec15f19a38771eb64b4a85c447c25 Reviewed-on: https://chromium-review.googlesource.com/c/1352110Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#611571}
-
Fergal Daly authored
Adds tests for manipulating it via the attribute. Renames PartNames() to Part() to match with part(), the API wrapper. This uses the same IDL as classList. Bug: 805271 Change-Id: I9715df48478510029f5d985124e46111c41cffc3 Reviewed-on: https://chromium-review.googlesource.com/c/1333014 Commit-Queue: Fergal Daly <fergal@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
-
liberato@chromium.org authored
This adds the Distribution class, which will replace the TargetDistribution typedef in Model. It provides some convenient functionality, such as += and max-finding. None of the uses of TargetDistribution are updated here. Change-Id: I0e86d9dbaddcd5421cbc65e73213329603346733 Reviewed-on: https://chromium-review.googlesource.com/c/1329881 Commit-Queue: Frank Liberato <liberato@chromium.org> Reviewed-by:
Fredrik Hubinette <hubbe@chromium.org> Cr-Commit-Position: refs/heads/master@{#611569}
-
Takashi Toyoshima authored
|response.head.headers| can be empty in some cases, e.g. ftp accesses. We previously added a null check in GetHeaderString(), but OnReceiveResponse() itself accesses it without any null check. This patch adds a check to have a status code, and uses a fallback value if it does not exist. Bug: 908261 Change-Id: I15e0e61ce39c9e7846c26ab8875485b4597ce458 Reviewed-on: https://chromium-review.googlesource.com/c/1351348Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#611568}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7f2a2ae33b38..8640c5d4e9f9 Created with: gclient setdep -r src-internal@8640c5d4e9f9 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:860880,chromium:892303 TBR=mmoss@chromium.org Change-Id: I18acbcb34b9104a93e1bcf5149a1becea85dfaa4 Reviewed-on: https://chromium-review.googlesource.com/c/1351760Reviewed-by:
-
DongJun Kim authored
https://google.github.io/styleguide/cppguide.html#Namespace_Names > Namespace names are all lower-case. This CL has no behavior changes. Bug: 889726 Change-Id: Icf64d8eaa44e8d4e2a321ae831379c483a765d14 Reviewed-on: https://chromium-review.googlesource.com/c/1352069Reviewed-by:
-
Nigel Tao authored
BUG=826982 Change-Id: Iede4849e94bbecc9340dcd3d612e419531185fa9 Reviewed-on: https://chromium-review.googlesource.com/c/1347955 Commit-Queue: Nigel Tao <nigeltao@chromium.org> Reviewed-by:
-
Roger McFarlane authored
This CL integrates ARIA label and description parsing into the render/JS to browser communication path. This allows the browser to have knowledge of the ARIA label and description. Bug: 896719 Change-Id: If5e8d9389f10beecae102080ebcde066aae6c80a Reviewed-on: https://chromium-review.googlesource.com/c/1342673Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Roger McFarlane <rogerm@chromium.org> Cr-Commit-Position: refs/heads/master@{#611564}
-
Chih-Yu Huang authored
Move the common macros to macros.h. This CL is just code refactoring, not changing any code logic. BUG=b:119794200 TEST=Run VDA unittest on Bob and Eve Change-Id: I066a5e79c58e9c95c3db714534bf9f309f8314a5 Reviewed-on: https://chromium-review.googlesource.com/c/1345751Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#611563}
-
Austin Eng authored
Add additional internal formats for CopyTexImage2D Unsuppresses previously failing test # for webgl2_conformance_expectations.py Bug: 905531 Change-Id: Ib9f525afa0188def6464c9f6134efc0090825f6b TBR: kbr@chromium.org Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_angle_rel_ng;luci.chromium.try:win_angle_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/1340369 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#611562}
-
Kent Tamura authored
A follow-up of crrev.com/611454. We had other instances of LAYOUT_TEST_PATH_PREFIX. TBR=qyesrsley@chromium.org Bug: 909012 No-Try: true Change-Id: Iec4c017f9123857f50e56ae3e8f5c6ae457af949 Reviewed-on: https://chromium-review.googlesource.com/c/1352087Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/36900aad7d96..cde48580e93d git log 36900aad7d96..cde48580e93d --date=short --no-merges --format='%ad %ae %s' 2018-11-28 lamontjones@chromium.org Add missing unit tests. 2018-11-28 dgarrett@google.com Reland generic_stage.GetRepoRepository: Make arguments flexible. Created with: gclient setdep -r src/third_party/chromite@cde48580e93d 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: Ib9820977399c623028a09c41feff07fe16fc06f3 Reviewed-on: https://chromium-review.googlesource.com/c/1352607Reviewed-by:
-
Darren Shen authored
This reverts commit 01dd4ead. Reason for revert: Seems to have broken fushcia cast: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/fuchsia-arm64-cast/2910 Original change's description: > Make BrowserWithTestWindowTests work with single process Mash > > The InputDeviceClient needs to only be created once, so remove it > from AuraTestSuiteSetup. Otherwise, in BrowserWithTestWindowTest, > it gets created twice: during test suite setup, and as part of > OzonePlatform (due to AshTestHelper/ash::Shell). > > Many tests still need one though, especially those that create a > WebContents, so add it to RenderViewHostTestEnabler, which should > take care of all RenderViewHostTestHarness tests or tests that create > the enabler manually. > > Also update a few other tests to either create their own > RenderViewHostTestEnabler or InputDeviceClient as appropriate. > > Also the InputDeviceManager can be a true singleton now (not thread- > singleton). > > Bug: 905430 > Change-Id: I2974968efe0415f0b56218e24b4fa546a1524fe1 > Reviewed-on: https://chromium-review.googlesource.com/c/1341075 > Reviewed-by: Scott Violet <sky@chromium.org> > Commit-Queue: Evan Stade <estade@chromium.org> > Cr-Commit-Position: refs/heads/master@{#611556} TBR=sky@chromium.org,estade@chromium.org Change-Id: Iadad5f76d31d82e8dc4cd427db184f536fdbef38 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 905430 Reviewed-on: https://chromium-review.googlesource.com/c/1352125Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#611559}
-
Wei Li authored
The test was disabled because ChromeOS will exit the test. But it is no longer the case on ChromeOS. Let's enable it. It is a bit weird to have this test inside tab_contents_iterator_unittest.cc since it has little to do with tab content. This CL moves the test to chrome/browser/lifetime/ since it tests whether AttemptRestart() sets the preference correctly. We also clean up the headers. BUG=none Change-Id: I663a0a7159b325b3783d816bec1d518ad7da7adb Reviewed-on: https://chromium-review.googlesource.com/c/1352573 Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#611558}
-
Mike Dougherty authored
This CL removes macro usage from /ios/chrome/browser/autofill. This CL was uploaded by git cl split. R=mahmadi@chromium.org Bug: 589840 Change-Id: I84f6c6f53c27df62ebd04b6bcc88a0e27ba67833 Reviewed-on: https://chromium-review.googlesource.com/c/1351959Reviewed-by:
-
Evan Stade authored
The InputDeviceClient needs to only be created once, so remove it from AuraTestSuiteSetup. Otherwise, in BrowserWithTestWindowTest, it gets created twice: during test suite setup, and as part of OzonePlatform (due to AshTestHelper/ash::Shell). Many tests still need one though, especially those that create a WebContents, so add it to RenderViewHostTestEnabler, which should take care of all RenderViewHostTestHarness tests or tests that create the enabler manually. Also update a few other tests to either create their own RenderViewHostTestEnabler or InputDeviceClient as appropriate. Also the InputDeviceManager can be a true singleton now (not thread- singleton). Bug: 905430 Change-Id: I2974968efe0415f0b56218e24b4fa546a1524fe1 Reviewed-on: https://chromium-review.googlesource.com/c/1341075Reviewed-by:
-
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: I9b2114b02f1b7cd9e6ca24a3db88e0d6675d82be Reviewed-on: https://chromium-review.googlesource.com/c/1352949Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#611555}
-
Sunny Sachanandani authored
This causes video corruption when swap chain is resized to a small size and then resized back to a large size. If the swap chain doesn't update after resizing back, it will remain with the smaller size. It's also likely that this causes video corruption issues with minimize and restore, and with the Aero peek live preview Windows feature. Split out from crrev.com/1305198 because that change is more risky and we want to wait until M72 branches to land it. Bug: 908069 Change-Id: I8a3edde507bca836dbf321b8ebc4e486415d193b Reviewed-on: https://chromium-review.googlesource.com/c/1352771Reviewed-by:
-
Hiroki Nakagawa authored
This CL moves WebWorkerFetchContext creation from ThreadedMessagingProxy::StartGlobalScope() to Dedicatedworker::CreateGlobalScopeCreationParams() in order to put params construction in one place for code cleanup. Bug: 906991 Change-Id: I7a365bbc0706f271b61e9f56648f9b7a47506dd8 Reviewed-on: https://chromium-review.googlesource.com/c/1351199Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#611553}
-
Sunny Sachanandani authored
UMA data from experiment on Dev/Canary looks good. Keep the finch flag until M72 is branched to serve as a kill switch. Bug: 869677 Change-Id: I2bad591041f5b4c56d1e356069ac5b0364947d0d Reviewed-on: https://chromium-review.googlesource.com/c/1351281Reviewed-by:
-
Antonio Gomes authored
BUG=903873 Change-Id: I42f35c394e36350c0bd88c8131edc64b2e6d677f Reviewed-on: https://chromium-review.googlesource.com/c/1351159Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#611551}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/0bd32409b7b7..cf714a81c86e git log 0bd32409b7b7..cf714a81c86e --date=short --no-merges --format='%ad %ae %s' 2018-11-28 jiawei.shao@intel.com Add checks on the texture view used as color or depth stencil attachment Created with: gclient setdep -r src/third_party/dawn@cf714a81c86e The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-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: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: If3904770001e8839dcf3b228c82f04145ec9fdcb Reviewed-on: https://chromium-review.googlesource.com/c/1351136Reviewed-by:
-
Brandon Wylie authored
Since the CachedImageFetcher uses a disk cache, there's potential for flickering. Particularly for low-end devices. This adds an in-memory caching layer that clients can use to prevent flickering problems for latency-sensitive features. Bug: 889234 Change-Id: I2da010aabeb7619b01f55f6305a8a0670d2831cf Reviewed-on: https://chromium-review.googlesource.com/c/1343042Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#611549}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/3e2cdea95cd8..cb8a4ddc2277 git log 3e2cdea95cd8..cb8a4ddc2277 --date=short --no-merges --format='%ad %ae %s' 2018-11-28 thestig@chromium.org Get rid of "exceptions" in CBC_QRCoderBitVector::At(). 2018-11-28 thestig@chromium.org Get rid of "exceptions" in CBC_SymbolInfo::Lookup(). 2018-11-28 thestig@chromium.org Get rid of "exceptions" from CBC_EncoderContext ctor. 2018-11-28 tsepez@chromium.org Try to make pdf_cfx_barcode_fuzzer result more consistent. 2018-11-28 tsepez@chromium.org Remove CBC_PDF417::m_compact and m_compaction. Created with: gclient setdep -r src/third_party/pdfium@cb8a4ddc2277 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: Ie8e20561d1ea213a82d72b91f568c7ce286f29d1 Reviewed-on: https://chromium-review.googlesource.com/c/1352606Reviewed-by:
-
Mike Dougherty authored
This CL moves the handling of Javascript console logs to an improved architecture, but is a no-op in terms of functionality. This will allow Javascript logs to be exposed in non-debug builds (instead of printing them to the device console as is done currently). Bug: 899851 Change-Id: I25eedc1f450df48acf66e4306f8846e0f761276f Reviewed-on: https://chromium-review.googlesource.com/c/1338946 Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#611547}
-
Alexander Alekseev authored
Bug: 902564 Change-Id: Ia77cbc8986acc9c3767cb08dd2f50567b14ddf70 Reviewed-on: https://chromium-review.googlesource.com/c/1351464 Commit-Queue: Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#611546}
-
