fix: #1455 新版 App 桌宠兼容更新 / restore #1455 on newer Codex App#1484
Merged
BigPizzaV3 merged 1 commit intoJul 13, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
中文
#1455 新版 Codex App 紧急兼容更新(2026-07-13)
这是已合并 PR #1455 的后续兼容修复,希望能够尽快审查并合并。#1455 合并时已经通过真人测试,V2 桌宠真实鼠标朝向、原生 hover 交互和 Computer Use 优先级均正常;但 Codex App
26.707.8479.0随后改变了 V2 spritesheet 的渲染结构,导致已合并功能在新版 App 中无法识别桌宠并安全 no-op。如果本修复未合并,#1455 提供的“桌宠跟随真实鼠标”会在该新版 App 中保持不可用。为什么会失效
旧版 App 将 V2 spritesheet 渲染为桌宠节点下的
<img>,#1455 通过naturalWidth === 1536 && naturalHeight === 2288确认 V2 素材,避免错误驱动 V1 宠物。新版 App 不再创建该
<img>,而是将同一份1536×2288PNG 作为.codex-avatar-root的 CSSbackground-imagedata URI。功能本身和素材版本没有变化,但旧探针找不到<img>后会按设计停止注入,因此真实鼠标朝向完全失效。这是新版 App 渲染结构变化带来的兼容回归,不是 #1455 初始实现时就存在的问题。本次修改
<img>V2 尺寸检测,继续兼容旧版 App。background-imagePNG data URI 检测,只读取 Base64 头部并解析 PNG IHDR 宽高,不解码完整 spritesheet。1536×2288V2;1536×1872V1 和缺失素材继续安全拒绝。验证
26.707.8479.0现场检查:新版 CSS V2 spritesheet 可识别,热注入后运行状态恢复正常。cargo fmt --all -- --checkcargo test -q -p codex-plus-core --test cdp_bridge -j 2:77/77通过。cargo check -q -p codex-plus-launcher -j 2<img>V2 接受、CSS V1 拒绝、缺失素材拒绝。English
Urgent compatibility follow-up for #1455 on newer Codex App (2026-07-13)
This is a compatibility follow-up to merged PR #1455, and an early review/merge would be appreciated. #1455 was human-tested when merged: V2 real-mouse gaze, native hover interactions, and Computer Use priority all worked correctly. Codex App
26.707.8479.0later changed how the V2 spritesheet is rendered, so the merged feature can no longer identify the pet and intentionally no-ops on the newer App. Without this follow-up, the real-mouse pet gaze delivered by #1455 remains unavailable on that App version.Why it regressed
The previous App rendered the V2 spritesheet as a descendant
<img>, and #1455 safely identified V2 throughnaturalWidth === 1536 && naturalHeight === 2288to avoid driving V1 pets.The newer App no longer creates that
<img>. It renders the same1536×2288PNG as a CSSbackground-imagedata URI on.codex-avatar-root. The feature and sprite version are unchanged, but the original probe cannot find its<img>evidence and therefore stops injection by design. This is a compatibility regression caused by the newer App rendering structure, not a defect that existed when #1455 was introduced.Changes
<img>V2 dimension detection for older App builds.background-imagePNG data URIs by reading only the Base64 header and parsing PNG IHDR dimensions, without decoding the full spritesheet.1536×2288V2; reject1536×1872V1 and missing sprites safely.Verification
26.707.8479.0: the CSS V2 spritesheet is detected and the injected runtime becomes healthy again.cargo fmt --all -- --checkcargo test -q -p codex-plus-core --test cdp_bridge -j 2:77/77passed.cargo check -q -p codex-plus-launcher -j 2<img>V2 accepted, CSS V1 rejected, and missing sprite rejected.