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

オープン
#9,502 コメント 1 件 リアクション 0 件 担当者 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時間
マージ済み PR(30日)
185

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apache/texera のほかの issue

apache/texera の issue をすべて見る

似ている issue

Scala の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。