A dropdown opened in the operator property panel stays where it opened while the panel scrolls away beneath it

未关闭
#9,502 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@yangzhang75 已经在做这个了。

开始于 2026年11月16日。

评估

这个 Issue 还没有评估数据。

描述

What happened?

Open any dropdown in the operator property panel (an attribute nz-select, a type selector) on an operator whose form is taller than the panel, then scroll the panel with the wheel: the open list stays at its old screen position while its select scrolls away, so the list hangs in mid-air over whatever is now under it. The same happens on the Form View page, whose page scrolls, for any dropdown in a card (measured: scrolling the page moved a select 92 px and left its open list where it was).

Two causes, both needed:

  1. The scrolling element is not registered with the CDK. The list is a CDK overlay with a reposition-on-scroll strategy, and that strategy hears about scrolling only from containers registered as cdkScrollable; the panel's scroll container (#content, the overflow-y: auto element in property-editor.component.html) is not, nor is the Form View's host (:host is the scroller there). The window's own scroll is handled, inner scrollers are not.
  2. There are two @angular/cdk copies in the bundle. package.json pins @angular/cdk 21.2.14 and ng-zorro-antd 21.3.3; ng-zorro declares @angular/cdk as a regular dependency (not a peer) with the range ^21.0.0, which Yarn resolves to a second, nested @angular/cdk 21.2.8 under node_modules/ng-zorro-antd/node_modules (yarn.lock: "@angular/cdk@npm:21.2.14" and "@angular/cdk@npm:^21.0.0" → 21.2.8). Each copy has its own ScrollDispatcher, so a dropdown built by ng-zorro's overlay listens to one dispatcher while a cdkScrollable registered by the app lands in the other, and registering the scroller alone changes nothing for nz-select.

Expected: an open dropdown follows its select while the panel (or the Form View page) scrolls, as it does when the window scrolls.

How to reproduce?
  1. Add an operator with a long form and a dropdown (an Aggregate with several aggregations has attribute dropdowns; a Python UDF with a few extra output columns has type dropdowns) and open its property panel. The panel caps itself at 60% of the window height, so a form taller than that already scrolls; otherwise drag the panel's bottom resize handle up until it does.
  2. Open one of the panel's dropdowns, then scroll the panel with the wheel.
  3. The list stays put; the select slides away under it.
Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output

主要语言
Scala
星标
333
派生
202
平均合并
3 天 11 小时
30 天内合并 PR
185

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/texera 的其他 Issue

查看 apache/texera 的全部 Issue

相似的 Issue

更多 Scala Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。