- 19 Apr, 2019 40 commits
-
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/a16238df3f28..7dd3889f2cf7 git log a16238df3f28..7dd3889f2cf7 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 swiftshader.regress@gmail.com Regres: Update test lists @ a16238df Created with: gclient setdep -r src/third_party/swiftshader@7dd3889f2cf7 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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=swiftshader-team+autoroll@chromium.org Change-Id: I9445b73bd19fd80fa481b68dc237a1c340abd108 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575402Reviewed-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@{#652484}
-
Yao Xiao authored
and the request_initiator is the script origin. Also fixed 2 issues: - For the main resource request (serviceWorker.register(...)), it goes through FrameFetchContext::PrepareRequest() that will always set the top_frame_origin regardless whether it's from service worker. Adding a check for service worker seems to fix it. - The static function GetNetworkFactoryCallbackForTest() in embedded_worker_instance.cc returns an Optional of Callback, but the caller only checks the nullity of the Optional but not of the Callback. This sometimes is causing a crash in the test. Removing the Optional seems to fix it. Bug: 918868 Change-Id: I2a5b83d8b13b2d52310614dfb5a6dfa4d1cd620a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553948 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#652483}
-
Meilin Wang authored
This change expands the unit tests to cover the Assistant key remapping feature. Misc: fix typo and lint errors. Bug: None. Test: Local compile and run tests changed in this CL. Change-Id: I21a559a4d2cec07f581bcc3573034520c6c79c3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570806 Commit-Queue: Meilin Wang <meilinw@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#652482}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9f474a8e0e81..7f8529c21699 git log 9f474a8e0e81..7f8529c21699 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 benjhayden@chromium.org Display median and 90th% in multi-event-sub-view Created with: gclient setdep -r src/third_party/catapult@7f8529c21699 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=oysteine@chromium.org Change-Id: If6bb33f87052693a47491f230372f0a171a2f7c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575401Reviewed-by:
-
Yue Zhang authored
Add a layer of callback in MultiThumbnailCardProvider to fetch favicon and draw with shadowed circle background in thumbnail. Bug: 946286 Change-Id: Id4fce1c635d1f639778476730ba7cea131496376 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574639 Commit-Queue: Yue Zhang <yuezhanggg@google.com> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#652480}
-
liberato@chromium.org authored
This CL enables the following: - SupportedVideoDecoderConfigs are now returned from the GPU process as a map [video decoder implementation] => vector of SupportedVideoDecoderConfig for that implementation. - GpuVideoAcceleratorFactories::IsDecoderConfigSupported takes the implementation enum value as an additional argument, and checks only against that implementation's supported configs. - MojoVideoDecoder accepts an implementation enum during construction, which will be provided to the service during decoder initialization. - GpuMojoMediaClient uses the kAlternate implementation enum value to select D3D11VideoDecoder on Windows, if the experiment is currently enabled. It no longer uses FallbackVideoDecoder. - MojoDecoderFactory adds a kAlternate decoder, in addition to the kDefault decoder, on Windows if the experiment is enabled. - RTCVideoDecoderAdapter always selects the default video decoder implementation. This causes RTC on windows to use only DXVA, rather than D3D11VideoDecoder. This will be addressed as follow- up work, though likely not immediately. The main reason for this is that it lets the renderer's decoder selection algorithm see two MojoVideoDecoder instances: one for DXVA and one for D3D11VideoDecoder. This lets decoder selection and fallback happen normally for them, rather than having the fallback happen in the GPU process via FallbackVideoDecoder. Bug: 954422 Change-Id: If6f056723c11ff50327623ac8d554d9f5da9f499 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534984Reviewed-by:
Xing Liu <xingliu@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#652479}
-
Kenichi Ishibashi authored
Before this CL credentials.py tried to get "Origin" header value unconditionally and resulted in an internal server error. This CL changes credentials.py so that it sets "Access-Control-Allow-Origin" only when "Origin" header is supplied. Bug: 952266 Change-Id: I804d538cc24c2fb51d0c156400425e056d51fb7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575300 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
-
Jeremy Roman authored
It's what's expected per spec, and it's more efficient. Bug: 627682 Change-Id: I5462a9c34cf9a1b6f2825e9e0c58e3c64b8c1698 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575034Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#652477}
-
liberato@chromium.org authored
Since the enhanced unweighted tree experiment seems to give us good results compared to the weighted base / enhanced tree and base table, add unweighted variants of the base tree and table. The goal is to see if unweighted examples help more or less with the (a) base features vs enhanced features, and (b) with the table vs the decision tree. Change-Id: Ie5b5938d42f6085518662e2a198e0d8a10e92cdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570702Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#652476}
-
dpapad authored
Specifically: - cr.makePublic() was not used anywhere. - cr.getUid() was only used in one place, which is being replaced by using a Map instead. - cr.createUid() is still used, but only within cr.js, and therefore there is no need to export it on the cr namespace anymore. Note that the removal of cr.makePublic() also allows removing some code from https://github.com/google/closure-compiler/blob/master/src/com/google/javascript/jscomp/ChromePass.java Bug: None Change-Id: Ie1791cfac7c9c3658dff722556850a04dda81e80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575027Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Dan Beam <dbeam@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652475}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/ac58e63295f0..145ec7fa7c81 git log ac58e63295f0..145ec7fa7c81 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 kainino@chromium.org Revert "Define and expose EGL_ANGLE_power_preference extension." Created with: gclient setdep -r src/third_party/angle@145ec7fa7c81 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:2813 TBR=cwallez@chromium.org Change-Id: I8a909db355d5431ccb853b96e68eedddabe9512e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574437Reviewed-by:
-
Rakina Zata Amni authored
It's possible to be in a committing state without having a commit promise resolver, if the commit is caused by activation. This causes problems with commit() calls that happen on the same frame as activation-induced commit, as it expects the resolver to exist. This CL handles that case and adds a test. Bug: 953614 Change-Id: I83ba0b6e450672588ff960389fc045be4896fe32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573425Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Fergal Daly <fergal@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#652473}
-
Tao Bai authored
This case will be covered in Java integration test. Bug: 954387 Change-Id: I1b34a031d47e97fbcabd24f4363ce6ca9fe97579 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574946Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Tao Bai <michaelbai@chromium.org> Cr-Commit-Position: refs/heads/master@{#652472}
-
Keishi Hattori authored
This reverts commit 133ed70b. Reason for revert: Caused NewTabFromLinkOpensInGroup and others to fail https://findit-for-me.appspot.com/waterfall/failure?url=https://build.chromium.org/p/chromium.memory/builders/Linux%20ChromiumOS%20MSan%20Tests/builds/12442 Original change's description: > [Tab Groups] Stop using TabGroupData pointers as group IDs. > > Tab groups are currently identified using TabGroupData pointers. However, > this is fragile because those pointers may not be valid forever and > because memory address may be reused. It makes more sense to use an > opaque int ID for this purpose instead. This also allows the API to > explicitly define when a group may be null or not, by using > base::Optional. Also, in a future patch, tab_strip_layout.h/cc will be > able to operate using that ID and continue to avoid knowledge of any > particular View type. > > This patch also includes some miscellaneous refactoring in > tab_strip_model_unittest.cc. > > Bug: 905491 > Change-Id: I9700a50d5fa9e4050ec2169af8e1362d11d9dade > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562764 > Commit-Queue: Bret Sepulveda <bsep@chromium.org> > Reviewed-by: Peter Kasting <pkasting@chromium.org> > Reviewed-by: Taylor Bergquist <tbergquist@chromium.org> > Cr-Commit-Position: refs/heads/master@{#652391} TBR=pkasting@chromium.org,bsep@chromium.org,tbergquist@chromium.org Change-Id: I1ede97f8791b79649fbf6d98947fbb1567d8fee2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 905491 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575259Reviewed-by:
Keishi Hattori <keishi@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#652471}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 3d140e8c. With Chromium commits locally applied on WPT: 0a8f3ffa "Use testdriver Action API in WPT pointerevent touch tests - Part 2" 4e921520 "[Code Health] Remove unnecessary reference file for web test" 40465b74 "[Animation Worklet] Copy the effects of a migrating animator over to new global scope" e28269b6 "[LayoutNG/PE] Clear visual overflow for LayoutText before setting." Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: raphael.kubo.da.costa@intel.com, rijubrata.bhaumik@intel.com, timvolodine@chromium.org: external/wpt/generic-sensor NOAUTOREVERT=true TBR=raphael.kubo.da.costa No-Export: true Change-Id: I762bf86e2ad7c862ebaf7480c7560efb389cd2a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574433Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#652470}
-
Chris Lu authored
UMA over Cellular feature removes kMetricsReportingWifiOnly local pref. Tests will fail if retrieving or setting occurs. Bug: 931289 Change-Id: Ibda70e02dde35f50426f6501210130a8c2834be0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574837 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#652469}
-
Meilin Wang authored
This change adds a new flag in chrome://flags to enable Assistant key remapping in the keyboard settings. Bug: None. Test: local compile and manually test. Change-Id: I9708e705da6e9e012089a4559965cb2f431bd87f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573002 Commit-Queue: Meilin Wang <meilinw@chromium.org> Reviewed-by:
-
Lily Chen authored
See https://docs.google.com/document/d/19vDLCRVP-WvWxA_YNZfhkkW6fS5A2Ea9ulJ8i8AcPAM/edit?usp=sharing for details. This CL refactors the client side of the ReportingCacheImpl. Clients, endpoint groups, and endpoints are now represented by separate structs. The cache stores each in separate maps. Endpoints are evicted if an origin exceeds the per-origin endpoint limit, or if the cache exceeds the global endpoint limit. This fixes an incorrect assumption made by the previous implementation that a given endpoint URL cannot be in multiple groups for the same origin. Bug: 912951 Change-Id: I0c548c3cf20ac57a9f17482300dd9a57a14e53b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1453109 Commit-Queue: Lily Chen <chlily@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#652467}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/96fbe0810a3f..a16238df3f28 git log 96fbe0810a3f..a16238df3f28 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 chrisforbes@google.com Add support for OpAtomicCompareExchange 2019-04-19 chrisforbes@google.com Add support atomic instructions as used with storage images 2019-04-19 chrisforbes@google.com Add support for OpImageTexelPointer Created with: gclient setdep -r src/third_party/swiftshader@a16238df3f28 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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:b/130768731,chromium:b/127472316,chromium:b/130768731,chromium:b/127472316,chromium:b/130768731 TBR=swiftshader-team+autoroll@chromium.org Change-Id: I176d249ff7276933d0a27012a78d280db710657b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575358Reviewed-by:
-
Yoshifumi Inoue authored
This patch Introduces |CompositeEditCommand::RemoveAllChildrenIfPossible()| to avoid infinite root in |TypingCommand| and |DeleteSelectionCommand|. This patch is a continuation of the CL[1]. Note: no regression test as there's no minimized test case in the original report, and it's not worth the minimization because the bug is a rather edge case that requires an editable <style> element that specifies editable style on its parent using deprecated '-webkit-user-modify'. [1] http://crrev.com/c/1567098 [Editing] Abort TypingCommand when RemoveNode() fails to remove a node Bug: 949501 Change-Id: I9bd19da22f54cd7cbda735103c599a5082f8d94f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573434 Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#652465}
-
rbpotter authored
- Make cr-input's background color consistent with md-select - Fix the background of the search icon in Print Preview's search box cr-input, so that it is the same color as the rest of the input. Bug: 954416 Change-Id: Iecc5c342ef6bd7f9e0400642ab6bab117164a79a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575029 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
-
Matt Falkenhagen authored
These are no longer used following the launch of S13nServiceWorker. Bug: 926114 Change-Id: Ie9c74c0ed88d15f505c23c15a111271a96874566 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573427Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#652463}
-
Shu Chen authored
This makes the non-mojo-imf and mojo-imf have the consistent logic to handle key events. Bug: 937167 Change-Id: I90a9a8ce8a776a4144203062b56297d2fcb572f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574981Reviewed-by:
Lan Wei <azurewei@chromium.org> Commit-Queue: Shu Chen <shuchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#652462}
-
Jarryd authored
This change removes the feature flag that guards quota usage details and will thus enable the feature by default. Intent to Ship: https://groups.google.com/a/chromium.org/d/topic/blink-dev/lq83adC8QRo/discussion Bug: 904000 Change-Id: I729d807dcbe1861b7ae38296c2db96a42f0791a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570533 Auto-Submit: Jarryd Goodman <jarrydg@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#652461}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=kariah@chromium.org Change-Id: I379b273c6a440e753ce27eb8cbaac9fbbb93121f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575086Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#652460}
-
Rakina Zata Amni authored
There's a bug in TraverseNext that might cause a node to traverse back to itself, even though it should've traversed to another node, triggering an infinite loop. This is caused by treating inner WebContents as children of the main frame, and potentially adding the same node as a child of multiple nodes. This CL changes the child/parent frame tree node traversal in FindManager, such that we won't encounter these cases anymore. Bug: 942346 Change-Id: I030492cb4c8a2aa330c71a15f9f337eb7ed0f3b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1530219 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652459}
-
Takashi Toyoshima authored
Since CORS preflight cache can live for a longer time in OOR-CORS mode, we introduce an entry limit to the CORS preflight cache. Also this patch adds a metric to count cache entries. Bug: 736308 Change-Id: Icd0ed0664d4bc592e921a632126ba88d1425f50b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573519 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#652458}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/067b46c33eed..641336160936 git log 067b46c33eed..641336160936 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 manojgupta@google.com chromeos_config: Enable skylab for toolchain builders. Created with: gclient setdep -r src/third_party/chromite@641336160936 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I2e13b4066efe8b67d075a7f527cad6085f345e90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574371Reviewed-by:
-
Austin Eng authored
This allows us to know when errors have occured since the error handling API has not been implemented yet. Change-Id: Ic7f6b03b086393e5d25a54543ce9500c8e66bd2f Bug: 877147 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546059 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#652456}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/85a239d09128..ac58e63295f0 git log 85a239d09128..ac58e63295f0 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 kbr@chromium.org Define and expose EGL_ANGLE_power_preference extension. Created with: gclient setdep -r src/third_party/angle@ac58e63295f0 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:2813 TBR=cwallez@chromium.org Change-Id: I2be116ffebdaf7dc15a8fbf540f0994b5389ec8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574372Reviewed-by:
-
Matt Falkenhagen authored
This was needed for navigation preloads in the non-S13nServiceWorker path. It's obsolete following the launch of S13nServiceWorker. TBR=kinuko Bug: 926114 Change-Id: Ic808c733e4da886566567ce3036de0a65a810b40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572762 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ad74585cca1c..9f474a8e0e81 git log ad74585cca1c..9f474a8e0e81 --date=short --no-merges --format='%ad %ae %s' 2019-04-18 benjhayden@chromium.org Migrate cp-switch to es6 module Created with: gclient setdep -r src/third_party/catapult@9f474a8e0e81 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 BUG=chromium:950011 TBR=oysteine@chromium.org Change-Id: I6732014cacb097f379e462509469a5c6d3ebf4e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574370Reviewed-by:
-
rajendrant authored
Change-Id: I1e38e6d983a0f46c8ace24bfe19a97600f90675b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575127Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#652452}
-
Drew Fisher authored
Fuchsia's fdio_get_vmo_clone is documented as returning a read-only clone of the underlying VMO, but has long returned a vmo that is both readable and exec-capable. As we try to bring the implementation in line with the docs and make fewer APIs imply executability, we need to update callers to not rely on the implicit executability of the VMO, but to add that right explicitly. Bug: 954263 Change-Id: I4cc14e99b095d432f3163d7d85b70428393e83e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574688 Commit-Queue: Drew Fisher <zarvox@google.com> Auto-Submit: Drew Fisher <zarvox@google.com> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#652451}
-
Lambros Lambrou authored
This is a very simple refactor, to facilitate hooking in a token-exchange service. Bug: 954427 Change-Id: If7b7a3528cd38090c64d6ab4e6990793ff5469ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575128 Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#652450}
-
dpapad authored
This is in preparation of removing the custom cr.EventTarget implementation in favor of native EventTarget, which requires all subclasses to be ES6 classes, otherwise a runtime "Illegal invocation" error is thrown. Bug: 854268,778674 Change-Id: I77e4924d9e22eb58d90f35e5c7b37b5f61759649 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574212 Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652449}
-
Hector Carmona authored
Bug: 951840 Change-Id: I628d3c86af68f2b36231b2497bdabf701c7ad8b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574607Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#652448}
-
Bret Sepulveda authored
The following tests are passing now, so removing TestExpectations lines. * printing/list-item-with-empty-first-line.html * printing/quirks-percentage-height.html * virtual/threaded/printing/quirks-percentage-height.html * printing/subframes-percentage-height.html * virtual/threaded/printing/subframes-percentage-height.html TBR=forshaw@chromium.org Bug: 591500 Change-Id: I14e5781021d816fd78707e3c2a4df841e95959f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575028Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#652447}
-
Joey Arhar authored
WebRequestProxyingWebSocket currently ignores the user-agent override set by DevTools present in the additional_headers parameter of AddChannelRequest. This patch stores additional_headers and forwards them if they are not already overriden by an extension. Bug: 941433 Change-Id: I340d3358293bd0a56732b41f2db7e8e854c85486 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1544246 Commit-Queue: Joey Arhar <jarhar@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#652446}
-
Daniel Cheng authored
Mojo provides predefined kMaxValue for circumstances where these sorts of values would be useful, so defining _LAST is redundant. In this case, it's only used to handle the NOTREACHED() case in the enum traits; just map the NOTREACHED() case to something arbitrary. Change-Id: Ieaca8b83f051f75f64071542c6135a0ddaca8544 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570735 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Auto-Submit: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#652445}
-
