- 05 Nov, 2020 40 commits
-
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/ac59b0e049f7..5689d6741bc4 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: Id97167c9ee3a5a0ae1829a56d00fe2d9c96533c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521839Reviewed-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@{#824617}
-
Sammie Quon authored
This gives a general idea of how long the videos saved on file are. I looked into adding a test (ps1), but with the multi-threading and async operations I'm afraid it would be flaky, plus it saved some recording files locally. Test: manual Bug: 1140182 Change-Id: Ib471d6eae0a8c49321984d941fb0775f49ca11a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519853Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#824616}
-
Devlin Cronin authored
Pull the logic to load and localize a file out from ExecuteCodeFunction. This will be useful in the upcoming scripting.executeScript() API. This CL has no functional changes. Bug: 1144839 Change-Id: I587aa928a9526ae494a6208ba5debb7789f5c01a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518113 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#824615}
-
Devlin Cronin authored
GetOverrideChannelForActionType() was used to generate a channel override if one was needed for a given action type, which was necessary when the "action" key was channel-restricted. Since it's now available on all channels, we can remove this method. Bug: 893373 Change-Id: I6a47eb93c2becf6df3cdcaef76b29ff7e75387ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2473063 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/ad54c71632cc..3476ca348bd0 2020-11-05 amaiorano@google.com Subzero: fix invalid arg access on Windows x86 for split variables 2020-11-05 amaiorano@google.com Subzero: fix non-deterministic stack layout and code-gen 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: I1e03d21535681fdbdf25360d7399803325e32c27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521992Reviewed-by:
-
Xida Chen authored
Currently the canvas and JSAnimation tracker isn't reporting to UMA. The problem is that after we set HasCanvasInvalidation and HasJSAnimation on the main thread, we didn't push to the impl thread, and thus there is no tracker started. This CL fixes the problem, also added to UKM so that we will also receive data for UKM. The original doc for collection UKM is here: https://docs.google.com/document/d/1SDxdua997Gm7ihJFVjinHz9qTdBzTJrEzC7GEeQHs-8/edit#heading=h.k5jx6iluw4yt Bug: 1141901 Change-Id: I0e1b0aaad8e35e2e8ab77356a81487782ad9ebde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2497464Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#824612}
-
Mikel Astiz authored
The metrics continue to be relevant to monitor the reuploading of bookmarks. Change-Id: I330b96ab95402b701cea5540fddaf35c925d6d8e Bug: 1104998 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518046Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Steven Holte <holte@chromium.org> Auto-Submit: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#824611}
-
Eugene But authored
This CL adds 2 new histogram. One for cert policy cache stored for Tab and one for all Tabs. Bug: 1140990 Change-Id: I03de0330759915974b4c89ceb7ee929d0118a53e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519153 Commit-Queue: Eugene But <eugenebut@chromium.org> Auto-Submit: Eugene But <eugenebut@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#824610}
-
Peter Boström authored
This experiment is default-enabled and being launched to 100% stable. Bug: 1002162 Change-Id: I1b0927ceb51d41fd298d94f4e0e2fdcd31205168 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520813 Auto-Submit: Peter Boström <pbos@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#824609}
-
Torne (Richard Coles) authored
This is a reland of cdc6f38e Original change's description: > android: upstream missed manifest changes for Q/R. > > On Q+ we disabled audio capture as we have no way to selectively disable > it for incognito tabs, but this was missed when upstreaming Q. > > Chrome needs QUERY_ALL_PACKAGES permission on R+ to check for any > possible intent handler for URLs. This was added downstream but missed > while upstreaming R support; add it now. > > Bug: 948282, 1042023 > Change-Id: I4136beddcba0227ef6cfc2073f90d645151ce6bb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507575 > Reviewed-by: David Trainor <dtrainor@chromium.org> > Reviewed-by: Theresa <twellington@chromium.org> > Commit-Queue: Richard Coles <torne@chromium.org> > Cr-Commit-Position: refs/heads/master@{#823642} Bug: 948282 Bug: 1042023 Change-Id: I1eafcc9cf9398d2ae9c2e4ee3bcc5891354f954e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521077 Auto-Submit: Richard Coles <torne@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#824608}
-
Katie Dillon authored
Currently you can request a reference to the MainThreadTaskQueue as well as the underlying TaskQueue from the SchedulerHelper. In all cases, the TaskQueue is only used to directly get the TaskRunner. We don't need to return the TaskQueue here so this change returns a reference to the TaskRunner instead. This CL is a follow-up to this CL[1] and removes a spot where we need to return a raw pointer to the underlying TaskQueue. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2453591 Bug: 1143007 Change-Id: I40e751f77447c54961c0102ddb596ddcfb035f69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519718Reviewed-by:
Scott Haseley <shaseley@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Katie Dillon <kdillon@chromium.org> Cr-Commit-Position: refs/heads/master@{#824607}
-
Morten Stenshorne authored
Fixed by CL:2519715 TBR=ikilpatrick@chromium.org Bug: 829028, 1091797 Change-Id: I9fc33e490b1990fddd72b7321052c90e28d35597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522073Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#824606}
-
Sean Harrison authored
Add new flag for the cookies page redesign. Change-Id: Ia1b98c74f77c34c9169282b2a981a7006a444c5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510272Reviewed-by:
Martin Šrámek <msramek@chromium.org> Reviewed-by:
Brad Lassey <lassey@chromium.org> Reviewed-by:
Theodore Olsauskas-Warren <sauski@google.com> Commit-Queue: Sean Harrison <harrisonsean@chromium.org> Cr-Commit-Position: refs/heads/master@{#824605}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/5689d6741bc4..e3fee63a19d6 2020-11-05 treehugger-gerrit@google.com Merge "tracing: Deflake QueryServiceState test" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll 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 Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I7cf0b24377cbf55c969f85f7f7773c37aa9892aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521995Reviewed-by:
-
Michael Hansen authored
FastInitiationManager causes a crash when StopAdvertising() is called because we move the callback parameter twice. This fixes the issue by storing the callback as an instance variable. Bug: 1145850 Change-Id: I5d5f305b558e60e55d0df248305c6da03e15378e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521837Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Michael Hansen <hansenmichael@google.com> Cr-Commit-Position: refs/heads/master@{#824603}
-
Nohemi Fernandez authored
Adds a notification showing the user's email and avatar when cookies have been re-generated for their account. Bug: 1145592 Change-Id: I4a74c38f15a17ef9ec8d85632ca8b95dbca3fed8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520996 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/master@{#824602}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/26705ac9bdf3..f6834b901326 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 xialinyan@google.com,smcgruer@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: chromium:1145307 Tbr: xialinyan@google.com,smcgruer@google.com Change-Id: I819e51c0549a1d6cecb13a578f44c53a9479dd00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521996Reviewed-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@{#824601}
-
Liquan (Max) Gu authored
Changes: * Corrected 2 typos. * Removed unused methods in PaymentUiService. * Turned ChromePaymentRequestService.mIsOffTheRecord into a local variable. * Simplified triggerMinimalUI control flow. Change-Id: I142e7d9e807419fae71e05d00b92a6ff50d30c7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519899 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#824600}
-
Yuheng Huang authored
Doc: https://docs.google.com/document/d/1-1ijT7wt05hlBZmSKjX_DaTCzVqpxbfTM1y-j7kYHlc Usage: tools/perf/run_benchmark run UNSCHEDULED_tab_search --browser-executable=out/Default/chrome --story-filter=tab_search:top10:2020 tools/perf/run_benchmark run UNSCHEDULED_tab_search --browser-executable=out/Default/chrome --story-filter=tab_search:top50:2020 tools/perf/run_benchmark run UNSCHEDULED_tab_search --browser-executable=out/Default/chrome --story-filter=tab_search:top100:2020 Change-Id: I684024f9cf3264ac2ed4feca15c6059342a493c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461224 Commit-Queue: Yuheng Huang <yuhengh@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Reviewed-by:
Thomas Lukaszewicz <tluk@chromium.org> Cr-Commit-Position: refs/heads/master@{#824599}
-
Stefan Zager authored
During a BeginMainFrame(), LocalFrameView::UpdateAllLifecyclePhases will always be called while a DocumentLifecycle::AllowThrottlingScope is on the stack. Outside of a BeginMainFrame(), there are situations where we do a "force-unthrottled" lifecycle update, meaning that throttled frames are forced to run the update because there is no AllowThrottlingScope on the stack. We do this, for example, when performing a hit test that requires up-to-date layout, even in throttled frames. The thesis of this patch is: a force-unthrottled update should never paint. It may update the lifecycle to any state prior to paint, but it should not paint. This is an important axiom, because it enables a nice optimization: during a force-unthrottled update, a frame that would be throttled during a full, throttling-allowed update can skip paint invalidation. This is true because a force-unthrottled update *cannot* paint, so paint invalidation is unnecessary. This patch adds AllowThrottlingScope to LocalFrameView::UpdateAllLifecyclePhases, and it prevents side-channel violation of the only-paint-when-throttling-allowed axiom by adding this to LocalFrameView::UpdateLifecyclePhases: DCHECK(DocumentLifecycle::ThrottlingAllowed() || target_state < DocumentLifecycle::kPaintClean); The bulk of the code change is updating our test code to be more consistent with how we run lifecycle updates. In particular, any call to UpdateAllLifecyclePhases in test code should mirror, as closely as possible, the behavior of a full BeginMainFrame(), which means that LocalFrameView::RunPostLifecycleSteps() should also run. This patch adds LocalFrameView::UpdateAllLifecyclePhasesForTest(), and updates all call sites in test code to use it consistently. Finally, this CL cleans up the usage of AllowThrottlingScope, by removing unnecessary instances of it and getting rid of the DocumentLifecycle& parameter to the constructor, since it is unused. Change-Id: I64b6e19e983f5882e035824f995cb0bfc5f4e2a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518095Reviewed-by:Yi Xu <yiyix@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#824598}
-
Javier Fernández García-Boente authored
The CSS Text 3 specification states on its 'Phase II: Trimming and Positioning' section: https://www.w3.org/TR/css-text-3/#white-space-phase-2 3- A sequence at the end of a line of collapsible spaces is removed, as well as any trailing U+1680 OGHAM SPACE MARK whose white-space property is normal, nowrap, or pre-line. 4- If there remains any sequence of white space and/or and/or other space separators, at the end of a line: If white-space is set to pre-wrap, the UA must hang this sequence. It may also visually collapse the character advance widths of any that would otherwise overflow. Summarizing, other space separator are not considered as collapsible spaces and should be hang, or broken in case of 'break-spaces', according to the value of the 'white-space' property. This CL tries to implement such behavior, since we were not considering this kind of spaces in the hanging/collapsing logic. For now this change affects LayoutNG only, but it'll be implemented for Legacy in a different CL. Bug: 972952 Change-Id: Idb0aff05f7f423f5b62f5169177c0240917435a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1687411Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#824597}
-
Andre Le authored
Ensure we don't accidentally log PII by only logging the size. Bug: 1106937 Change-Id: I428ac50ea33b6bc5780fcf0fc47ca92cb151a612 Fixed: 1143033 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522190 Commit-Queue: Andre Le <leandre@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#824596}
-
Dale Curtis authored
Finally got around to generating test media for this issue... and it looks like the original fix was incomplete! We didn't read the full box header before parsing CoLL and SmDm atoms. R=cassew Fixed: 1123430 Test: Updated unittest. Change-Id: I7aca462f623cd12cb4842c2cfa1b0b9758ba2ab5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518898 Commit-Queue: Will Cassella <cassew@google.com> Reviewed-by:
Will Cassella <cassew@google.com> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#824595}
-
Bo Liu authored
kWebViewEnableVulkan is renamed to kWebViewDrawFunctorUsesVulkan. It is set automatically when webview detects on start up that hwui is using vulkan composite. This flag is then passed to renderer and gpu processes. Add kWebViewVulkan and default to true, and add it to webview dev ui. This only takes effect if kWebViewDrawFunctorUsesVulkan is set, and controls whether to use gl interop or vulkan composite. So with this patch, the control is mainly in hwui. If hwui uses vulkan, then webview will use vulkan composite. But it also allows the user to manually fallback to gl-interop path. Also force enable skia renderer and viz if hwui uses vulkan. Bug: 1141683 Bug: 1141686 Change-Id: I53b7ae0da22884fab3cd1a401baec057c4eda241 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513786 Commit-Queue: Bo <boliu@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#824594}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e5e8e66e9b4f..a2d6b31f66f5 2020-11-05 ethannicholas@google.com Additional SkSL benches 2020-11-05 michaelludwig@google.com Use GrTBlockList instead of SkAutoSTMalloc to reduce GrAtlasTextOp size 2020-11-05 johnstiles@google.com Allow constant propagation for negated constant-vectors and ints. 2020-11-05 michaelludwig@google.com Compact fixed state tracked in GrAtlasTextOp 2020-11-05 fmalita@chromium.org [svg] Minor parser tweaks If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC bsalomon@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-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 Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: bsalomon@google.com Change-Id: Ie75d6dea0f30a224c706d01c0157b76b183da114 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521774Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c07bd2f23d7e..56ea854ec5e7 2020-11-05 lexa.knyazev@gmail.com Metal: Allow unswizzled BC1 RGB If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC courtneygo@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;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: courtneygo@google.com Change-Id: I21110865b4ce509359c163a64b039795af0a50b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521634Reviewed-by:
-
Mason Freed authored
This CL implements most of the suggestions from [1], which effectively block declarative Shadow DOM from being used by any fragment parser entry point, unless an explicit opt-in is toggled. The opt-ins include: - DOMParser.allowDeclarativeShadowDom = true; - HTMLTemplateElement.allowDeclarativeShadowDom = true; - XMLHttpRequest.allowDeclarativeShadowDom = true; - DocumentFragment.allowDeclarativeShadowDom = true; - Document.allowDeclarativeShadowDom = true; // For innerHTML - A new <iframe> sandbox flag: allow-declarative-shadow-dom This mitigates the potential client-side XSS sanitizer bypass detailed in the explainer and at [1]. Assuming these changes are functional, and mitigate the issue, this new behavior will be folded into the spec PRs at [2] and [3]. But given the security implications of the existing code, I'd like to get this landed first. [1] https://github.com/whatwg/dom/issues/912#issue-733465826 [2] https://github.com/whatwg/html/pull/5465 [3] https://github.com/whatwg/dom/pull/892 Bug: 1042130 Change-Id: I088f28f63078a0d26e354a4442494c0132b47ffc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513525 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#824591}
-
Liquan (Max) Gu authored
Changes: * PRService takes over PaymentAppFactoryDelegate, PaymentAppFactoryParams from CPRService. These two interfaces need to be moved together, otherwise it would be subjected to the use-after-close issue of CL[1]. * Removed @Nullable from PRService#mPaymentOptions because it's not possible to be null[2]. * Wrapped canUserAddCreditCard in supportPaymentSheetBasedPaymentApp, because "whether users can add credit card" is not at the same semantic level as other methods of PaymentRequestService. PRService knows about basic-card payment app, and CPR knows about whether users can add credit card on the basic card payment app. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2519759 [2] https://source.chromium.org/chromium/chromium/src/+/master:components/payments/content/android/java/src/org/chromium/components/payments/PaymentRequestService.java;l=259;drc=df872ce8fcce25af51aa6b0f9fe8b1135b687524 Bug: 1146049, 1146051, 1145803 Change-Id: Ib02f9d15b4e0777e55d63770ec6f2b68b9fe6b3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520277 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
-
Daniel Hosseinian authored
Simultaneously, put existing event types in enums. Bug: 1134208 Change-Id: Ia4a3d7f6d03c0969b1f18961db0899a8a7f51b9e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2512368 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#824589}
-
Luke Zielinski authored
wptMetadataBuilder for desktop wpt bots. This will give us a clearer picture of what the true status of tests are in preparation for triaging them. Bug: 1142905 Change-Id: If0dc015ef3f7633f209ca2bd2a94c55f8ee77c76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503772Reviewed-by:
Robert Ma <robertma@chromium.org> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#824588}
-
Francois Beaufort authored
VideoCaptureDeviceFactoryAndroid was getting zoom support for each device every time when enumerating devices. This was problematic on some devices where opening a camera breaks existing stream for that camera. This CL adds cache of zooms in VideoCaptureDeviceFactoryAndroid. This allows to workaround the bug by getting zoom support only once for each device. Bug: 1138608, 934063 Change-Id: I52895ee5a538c44ce2ff53bc27714da88b9be54b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517465 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#824587}
-
Abigail Klein authored
caption bubble. If 5 seconds pass with no activity, hide the caption bubble. Activity is defined as one of the following occurring: - Transcription received from the speech service - User interaction, such as clicking a button or focusing the bubble More refinements to this will occur in a follow-up, such as clearing the caption text. Bug: 1055150 Change-Id: I33c96c09bc89bbfe68b1c8899f3aa5289ed44f76 AX-Relnotes: N/A (feature has not launched) Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518129Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Abigail Klein <abigailbklein@google.com> Cr-Commit-Position: refs/heads/master@{#824586}
-
Eugene But authored
According to Stability.iOS.UTE.MobileSessionAppState, a large number of Unexplained Termination Events happen in background. There is an assumption that "clean exit beacon" does not get written because prefs file is protected. This CL allows removing protection in the experiment. The experiment will be run on Canary and Dev to test the assumption. There is no intention to roll this out to Beta or Stable. If experiment will confirm the assumption, then clean exit beacon file will be decoupled from prefs to remove the protection. Bug: None Change-Id: If816c4b3ed28ba5b2649e63526d5cfea93f839c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506175Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#824585}
-
dpapad authored
In preparation of moving all IDR_WEBUI_JS_* resources to webui_generated_resources.grd, the new webui_generated_resources.pak file needs to be included in fuchsia/engine/. Bug: 1132403 Change-Id: I5c762bb01d30401866b266f9b9c374636e78ec69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521841 Auto-Submit: dpapad <dpapad@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Commit-Queue: dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#824584}
-
Chong Gu authored
Add fuchsia-board-astro tag. Apply tag to flaky/failing tests. Bug: 1080853 Change-Id: If2c42204b690ac8b6ccf3e47d2edea91e73ef622 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520719Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Auto-Submit: Chong Gu <chonggu@google.com> Cr-Commit-Position: refs/heads/master@{#824583}
-
Scott Violet authored
When history adds a page with redirects the transition qualifier is not applied to redirects. This resulted in FROM_API_3 being dropped, and pages that should be hidden being shown. This patch adds FROM_API_3 to CHAIN_END if FROM_API_3 was present in the requested transition. It's only necessary to add for CHAIN_END, as CHAIN_END must be present in order for the visit to be considered visible. BUG=1145208 TEST=HistoryBackendTest.AddPageWithRedirectsAndFromApi3IsNotVisible Change-Id: I4ac41e5385fe58b249532f1251612b6c1112005b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521833 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#824582}
-
Allen Bauer authored
Add metadata - remove manually overridden GetClassName. Add view builders and update view tree construction to use the builder. TBR=katie@chromium.org Bug: 772945, 938501, 1130078 Change-Id: Id105b26afb15138ee6e70e7ade5e43be11671a47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505880Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Reviewed-by:
Tetsui Ohkubo <tetsui@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Auto-Submit: Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#824581}
-
Daniel Cheng authored
Bug: 1131879 Change-Id: I12e46e7c7edcbf41a6c51b5f2210a3eaed1412ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521872Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#824580}
-
Ben Pastene authored
crrev.com/i/3385048 allocates the machines for these builders, so this can't land until that is deployed. Bug: 1140727 Change-Id: Ib09a59fdfd0aa4bba54a091606c08f76b59c48f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521352Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#824579}
-
Evan Stade authored
Bug: 1144109 Change-Id: I2b61d941b7538cbb504e2b8bab87b9ff2091169a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520201Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#824578}
-
