- 26 Aug, 2020 40 commits
-
-
Owen Min authored
This flag is introduced with https://codereview.chromium.org/250383004 as a way to disable the feature. Give that the feature has been launched for many years, we probably don't need this anymore. And it gives user a way to escape component cloud policy on desktop. Bug: 1119515 Change-Id: Icefcdc2ea49d9b25dbb535616befef427a53ee90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364960Reviewed-by:
Sergey Poromov <poromov@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#801844}
-
Jia Li authored
- Service launch/termination/crash: makes the implementation of `ServiceConnection` to observe and log these events. - Model loading/evaluation result/latency: directly log measurements from the ML Service. Bug: 1108337 Change-Id: I021c82a2a9b2aadec9402b392b82cb18d6076083 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362337 Commit-Queue: Jia Li <jiakl@google.com> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Reviewed-by:
Sophie Chang <sophiechang@chromium.org> Cr-Commit-Position: refs/heads/master@{#801843}
-
Yusuf Sengul authored
Bug: 1119466 Change-Id: Iba472f30a4e5f9625f85a94d1a8e1d67999961cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363216Reviewed-by:
Rakesh Soma <rakeshsoma@google.com> Commit-Queue: Yusuf Sengul <yusufsn@google.com> Cr-Commit-Position: refs/heads/master@{#801842}
-
Alexander Dunaev authored
This is a follow-up to [1] where it had been noted that the JavascriptAppModalEventBlockerX11 does not depend on anything X11 and should be renamed. This CL only renames one class. No changes to any logic are intended. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2366745 Change-Id: I711abba94bef47d17f14e401be6ef7af2a272eaf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377485 Auto-Submit: Alexander Dunaev <adunaev@igalia.com> Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#801841}
-
Chromium WPT Sync authored
Using wpt-import in Chromium b4b787f0. With Chromium commits locally applied on WPT: 9f52c7e4 "COOP: add reporting to redirects" d18db804 "Fix test flake in animation-state-changes-positive-playback-rate.html" 461d94a8 "Never re-use the layout result from the fieldset contents wrapper." 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: futhark@chromium.org, andruud@chromium.org, ericwilligers@chromium.org, shend@chromium.org: external/wpt/css/css-cascade NOAUTOREVERT=true TBR=robertma@google.com No-Export: true Change-Id: Ia02d8e35b219f64621dbe0f9e33e4725904b0dcb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377426Reviewed-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@{#801840}
-
David Morejon authored
This is an automated transformation using https://github.com/Ecosystem-Infra/web-test-transformer. The tool verifies its transformations, all of these files run successfully after transformation. See the tool output: https://gist.github.com/dmorejon/8383b6b532b13b0446d3398d8bc13593 This commit is the raw tool changes. There might be some stylistic changes to be made manually. Bug: 1120356, 936364 Change-Id: Ia5ba295bf83312d4951e548cf0d078ff1d4506f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368851Reviewed-by:
Robert Ma <robertma@chromium.org> Reviewed-by:
Luke Z <lpz@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#801839}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/622558b02e1a..1f48854dae26 2020-08-26 capn@google.com Refactor image extent retrieval 2020-08-26 capn@google.com Refactor image view extent retrieval 2020-08-26 capn@google.com Refactor image query instructions If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Iea7788d582d7e134425b46167f9d4a0076be51ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378170Reviewed-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@{#801838}
-
Scott Violet authored
Currently navigations triggered from the embedder use a navigation type of LINK. LINK navigations (mostly) result in processing intents. This is not always desirable (for example, the SRP shouldn't trigger intents). This patch adds the ability to disable Intent processing. I went with a function to disable vs an explicit setter as I don't think we need support for an absolute 'true' case. By that I mean if I did add a function like setIntentProcessingEnabled(boolean value), the implication is 'true' means intent processing always happens. In code that isn't the case though, for example, a same host navigation may not trigger intent resolution. As we don't need the ability to force intent processing, I'm avoiding it for now. BUG=1119365 TEST=covered by android tests Change-Id: Ib374c1d61ce0795654a677b1ff29128f39c75bd9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369516Reviewed-by:
Darin Fisher <darin@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#801837}
-
Scott Violet authored
This gives the core stability metrics. BUG=1120537 TEST=covered by weblayer_browsertests Change-Id: I22e99959dacb9b9593af02cea70088d449e604a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376565Reviewed-by:
-
Omer Katz authored
Change-Id: Ia475d5bd55bbf621c26c782c25d40b861a9de817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376821 Commit-Queue: Omer Katz <omerkatz@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Auto-Submit: Omer Katz <omerkatz@chromium.org> Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/master@{#801835}
-
Gavin Williams authored
This change guarantees the USB printer config and the print job notfications only use the OffTheRecord(OTR) profile to open System Web Apps(SWA) in Guest mode. There is an existing check (https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/browser.cc;l=471) that only OTR guest profiles are allowed to open SWAs. Change-Id: I78aef11b2d2cb8377f17ecd90f494828119ddf1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2372909Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Commit-Queue: Gavin Williams <gavinwill@chromium.org> Cr-Commit-Position: refs/heads/master@{#801834}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/7f786caa5d60..09ec5ae5729e 2020-08-26 chrome-bot@chromium.org Update config settings by config-updater. 2020-08-26 dburger@chromium.org Don't blow up when fsi config has no applicable models. 2020-08-26 engeg@google.com chromeos_config.py: fix typeo 2020-08-25 pprabhu@chromium.org Update test platform OWNERS 2020-08-25 kevinruvalcaba@google.com Added support for histogram creation. 2020-08-25 mmortensen@google.com contrib scripts: Change from prodaccess to gcert. 2020-08-25 pprabhu@chromium.org cbuildbot: Bump skylab tool version 2020-08-25 mmortensen@google.com query_build_logs: Change from prodaccess to gcert. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: Iefae62b0ce0d17ec3f668a69fc745d8757397db5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378189Reviewed-by:
-
Sundoo Kim authored
Explicitly remove the copy constructor and assignment operator with the delete keyword. Bug: 1121520 Change-Id: I8902f847eea98a129ee50822fee5e893d6310f4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377006Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#801832}
-
Avi Drissman authored
The OOM death tests used an allocation value of MAX_LONG minus 12k. The problem with that value is that, on systems like the Mac DTKs that have 16k VM pages, that gets rounded up and wraps. Therefore, abstract it into “subtract three pages”. Bug: 1121749 Change-Id: I6c519200cbd848c095b741d78f51317ea6ef18b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376887 Commit-Queue: Avi Drissman <avi@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Auto-Submit: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#801831}
-
Matt Menke authored
The NetLogViewer automatically resolves "net_error" fields to net::Error errors, but does do that for "error". I believe this will require a followup CL to update where the NetLogViewer's DNS tab gets network error string from. Fixed: 1122054 Change-Id: Ifd74a988999d6142634f412e73929f568af536ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375602 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#801830}
-
Chong Gu authored
This will add ~20 minutes of bot time and ~2 minutes of run time per build. The bots required to run these tests have been approved in crbug.com/1100546 Bug: 1058255 Change-Id: I542bce2dae6b8d0c84d50d8b595044445c31f406 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377306 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Auto-Submit: Chong Gu <chonggu@google.com> Cr-Commit-Position: refs/heads/master@{#801829}
-
Linkun Chen authored
To hide internal folder names. Test: build locally with internal change Bug: b/165815398 Merge-With: eureka-internal/442206 Change-Id: Ibb17c47f37c796d2513ad1b6dfd52a282903bddf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373289Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Linkun Chen <lkchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#801828}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/e23bb2ed..46f5bd5e Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues 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 CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I6120f4baa4d74393235fb1aecc5b8b2226361ad8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377427Reviewed-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@{#801827}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/fb9ee39c41d4..f60cabfb25c4 2020-08-26 tvanderlippe@chromium.org Typecheck bindings/CSSWorkspaceBinding.js with TypeScript If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I50b1279828bdd88bc077c5cb79ec7eb92ff059e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378190Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/7023f47299aa..0fdfdcf61cd4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Ic987c90c981da679d5d0a34316dabfb3f45fcef9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378086Reviewed-by:
-
Peng Huang authored
Bug: 1034840,1122020 Change-Id: Ia2dceed245c16b66d35b513f614656a27acde076 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377231 Commit-Queue: Peng Huang <penghuang@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#801824}
-
Brandon Wylie authored
This reverts commit c4aceb16. Reason for revert: ContactsPicker tests failing on android-bfcache-rel see crbug.com/1122069 Original change's description: > Move Contacts Picker to //components/browser_ui/contacts_picker > > Bug: 1016938 > Change-Id: Ib3a86b4a3e3c0356c292ce55291ef0487e94c5ae > Skip-Translation-Screenshots-Check: True > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2325272 > Commit-Queue: Evan Stade <estade@chromium.org> > Reviewed-by: Will Harris <wfh@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Lijin Shen <lazzzis@google.com> > Reviewed-by: Ted Choc <tedchoc@chromium.org> > Reviewed-by: Finnur Thorarinsson <finnur@chromium.org> > Cr-Commit-Position: refs/heads/master@{#801610} TBR=dcheng@chromium.org,finnur@chromium.org,estade@chromium.org,tedchoc@chromium.org,wfh@chromium.org,lazzzis@google.com Change-Id: Ie79da9732fafd575886793b15fc6b1bcf908d9cb No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1016938 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378268Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Commit-Queue: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#801823}
-
Amr Aboelkher authored
This reverts commit 3bc91ccc. Reason for revert: Failure of WebKit Linux ASAN build, and that's the suspect for root cause. See https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20ASAN/17329 Original change's description: > [Perfect Negotiation] Surface session descriptions at the right time. > > This fixes another timing related issue that blocks Perfect Negotiation. > > Before this CL, current/pending local/remote description attributes do > blocking-invokes on the webrtc thread, fetching the most up-to-date > states. This can prematurely expose the result of "in-parallel" > operations that have not surfaced yet, such as: > - setLocalDescription > - setRemoteDescription > - addIceCandidate > > This CL fixes that by copying the SDP states when any of these > operations complete on the WebRTC thread and carry them over in the > PostTask to the main thread. Here, we store these snapshots in > "internal slots" (variables living on the main thread). With this CL, > reading SDP attributes from RTCPeerConnection is non-blocking and > spec-compliant. > > WPT test coverage added for the exact timing of SLD/SRD and other test > expectations are updated. addIceCandidate updating the SDP is already > covered by old WPTs. > > Bug: chromium:1110347 > Change-Id: Id41ec354465525c6cedf631fe2209fe097148f60 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2323359 > Commit-Queue: Henrik Boström <hbos@chromium.org> > Reviewed-by: Harald Alvestrand <hta@chromium.org> > Cr-Commit-Position: refs/heads/master@{#801798} TBR=hta@chromium.org,hbos@chromium.org Change-Id: I4af12fd1430773ea3d134cfc37b9c5e736f20ed0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1110347 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377715Reviewed-by:
Amr Aboelkher <amraboelkher@google.com> Commit-Queue: Amr Aboelkher <amraboelkher@google.com> Cr-Commit-Position: refs/heads/master@{#801822}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/95c5b87ad1a3..ee3d26b3cdc2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC sahel@google.com,amraboelkher@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: sahel@google.com,amraboelkher@google.com Change-Id: I36b0ee36306f65fd58bc14f2e2b4645dd86dd5f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378165Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
-
Dave Tapuska authored
The code previously added an IME guard but it was removed when moving this into blink and the showing/hiding of the virtual keyboard was done on the HandlingInputState object itself. (via change https://chromium-review.googlesource.com/c/chromium/src/+/2212805). he IME guard prevents intermediate changes when handling an event. This was problematic for TinyIME because the text input mode changed between the processing of the event which caused the virtual keyboard to be dismissed. This change makes the code behave exactly the same before the move to blink. It can't be merged into M85 due to that branch only having part of the changes. So if it needs to go there it will need to be written separately. BUG=1121179 Change-Id: Ida425dedd240a3c2e36b458d45f04433c6d31963 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373363 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Auto-Submit: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#801820}
-
Brian Sheedy authored
This reverts commit 8c97b259. Reason for revert: Suspected culprit of crbug.com/1121810 Original change's description: > WebGL: Add a direct uploading path for texImage2D with video frame backed by GPU > > Current fast path for webgl uploading video frame is to render YUV planars to a RGBA8 > intermediate gl texture and than do gpu to gpu copy to update the dst webgl texture. > > It is possible to further optimize this progress by drawing the content from YUV planars > to dst webgl texture directly. This will save the extra gpu-gpu texture copy which may > hurt performance when uploading large resolution video (e.g. 4k/8k video). > > BUG=1108154 > > Change-Id: I0abb269944f9eac9fb77e13b01860152a918ad95 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319543 > Reviewed-by: Brian Salomon <bsalomon@google.com> > Reviewed-by: Dan Sanders <sandersd@chromium.org> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Commit-Queue: Shaobo Yan <shaobo.yan@intel.com> > Cr-Commit-Position: refs/heads/master@{#800811} TBR=bsalomon@google.com,kbr@chromium.org,jie.a.chen@intel.com,sandersd@chromium.org,shaobo.yan@intel.com,khushalsagar@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1108154, 1121810 Change-Id: I24a1ddd58e1c29c96bc65e566cf5eb34b26b5f4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376379Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#801819}
-
Roman Sorokin authored
This fixes the issue when both Enrollment screen and Login screen trying to load Gaia at the same time. SigninPartitionManager cancels one attempt to start another one. This might break the enrollment flow when Chrome can't extract oauth_code from the cookies partiton. It's a bit hard to test as it's a race condition. I will add something in a follow-up. Bug: 1119411 Change-Id: I81c7031ae05b2882f4e86feac63e1aee9058c13e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375426Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#801818}
-
Tommy Steimel authored
Bug: b:166321735 Change-Id: I53aa13485ac9f014c6ebc0ab8bf38f65204e0637 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375600Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#801817}
-
Tibor Goldschwendt authored
+ Shrink Kaleidoscope module according to spec. + Add closure compiler annotation to module descriptor. Change-Id: Id99185a8b1ee62d154cc663d2d525beaa91a29b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376460 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
-
Joanmarie Diggs authored
Text alignment and indentation are being exposed as object attributes to support IA2 and minimize work needed to calculate attributes which can only apply to an entire object. However, ATK treats alignment as a text attribute and platform ATs expect text-attribute-changed events (there is no object-attribute-changed event in ATK). Therefore, fire an AtkText text-attribute-changed event to notify ATs when either of these text properties change. It is up to platform ATs to check object attributes for these properties. Bug: 1108872 AX-Relnotes: Orca now includes alignment and indentation when its font- announcement command is used in Chrome/Chromium. It will be possible for Orca to add support for presentation of changes to these properties. Change-Id: I971777ba4a5f672bf129a4687ff2c54c250c41f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343267 Commit-Queue: Joanmarie Diggs <jdiggs@igalia.com> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#801815}
-
Noah Rose Ledesma authored
This change removes the need for communication between the audio device picker UI and the MediaNotificationService. This communication is now done via the UI's delegate class. Bug: 1121367 Change-Id: Ie541b1a3c65a8035fbbdb736bd9c4b9a3cbb89c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373270 Commit-Queue: Noah Rose Ledesma <noahrose@google.com> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#801814}
-
Christian Larson authored
CaptureEngine is used for VideoOnly so no need to initialize both audio and video. This can cause permissions issues or extra delay during initialize. Note this will fix GUM behavior for video only but not change the GUM with audio behavior. Bug: 1120716 Change-Id: Iaa9147f3e18804d663bf0a4c1163aa9327ea4f71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376366 Commit-Queue: Christian Larson <chrila@microsoft.com> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#801813}
-
Chris Findeisen authored
Provides some helper functions for adding this build info standardized into other crash contexts. BUG=1116135 Change-Id: I597222868a16003ab9c8fa42de1979e10d771807 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354496 Commit-Queue: Chris Findeisen <cfindeisen@chromium.org> Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#801812}
-
Yuta Hijikata authored
As part of an effort to unify logs in Chrome OS, this adds option to enable syslog-compatible log format for chrome for chromeos. e.g. 2020-06-27T23:55:25.094701Z ERROR chrome[3816:3877]: [drm_device_handle.cc(90)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s) For more detail http://go/cros-syslog-format-log-chrome. Related patches: crrev.com/c/2311981 Update tast test. BUG: 1093033 TEST: base_unittests Cq-Depend: chromium:2326511 Change-Id: I55053807d9291dce3b09d3d2e780501fa9383938 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2260255 Commit-Queue: Yuta Hijikata <ythjkt@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#801811}
-
Alice Wang authored
This CL batches AccountPickerBottomSheetTest. Bug: 1120258 Change-Id: I0f6ae90b8863aa3dafed3d016086e2f19cca3aae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376816Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#801810}
-
Victor Costan authored
Bug: 488553 Change-Id: I8e138d56c3cf3216997c070ed1545256262ad8a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371603 Auto-Submit: Victor Costan <pwnall@chromium.org> Commit-Queue: Eric Roman <eroman@chromium.org> Reviewed-by:
-
sauski authored
It is possible to access some forms of client storage while an opaque origin is currently the top frame origin. These serialise to the string 'null' and are of no use to access context auditing. This CL stops the service from recording accesses where the top frame origin is opaque. Bug: 1121932 Change-Id: I90d7c5a48a4f30deb71d5cec3c2ddf5d8d7f97d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377488Reviewed-by:
Martin Šrámek <msramek@chromium.org> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/heads/master@{#801808}
-
Clemens Arbesser authored
Bug: b/166429363 Change-Id: Ib20ad349a2f1e5efe5e1d6171ddee9563c7cb125 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377491Reviewed-by:
Luca Hunkeler <hluca@google.com> Commit-Queue: Luca Hunkeler <hluca@google.com> Auto-Submit: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#801807}
-
Eleonora Rocchi authored
This CL adds the logic to close the view dialog of a compromised credential if the reauth time expired. It also adds a test to verify the dialog is correctly dismissed. Bug: 1119796, 1092444 Change-Id: Icbab80bcb312a2d9ac81edacab1f6eb56e3eda23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377810Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Commit-Queue: Eleonora Rocchi <erocchi@google.com> Cr-Commit-Position: refs/heads/master@{#801806}
-
Nnamdi Theodore Johnson-Kanu authored
Bug: 1111477 Change-Id: Icaaaed1d8373c6071992b2936ff34d7c485e5c70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376311 Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#801805}
-
