Conversation
HANDOFF_FIREFOX_AMO.md records where the session ended: v1.1.2 is tagged, packaged and AMO-clean (0 linter errors, credentials verified), but must NOT be submitted because of #149. Also adds `--click` to scripts/firefox-smoke.mjs, which is what found #149. It clicks a verdict badge and asserts a visible overlay iframe, then reports whether the extension iframe ever became visible. Without it the Firefox build looked green: addons-linter passed and all 8 badges rendered while the interactive UI was dead. Static validation and "does it render" are not sufficient signals for a store submission. Reproduce the blocker: AUTO_SCAN=true TRUST_DEV_FIXTURES=true bun run build bun run serve:fixtures & node scripts/firefox-smoke.mjs --source-dir dist/firefox --min 5 --click Expect `OVERLAY VISIBLE: NO` and exit 1 until #149 lands. The handoff also carries the open decision (single branch + port relay + src/platform.ts, with the churn evidence behind it), the unconfirmed popup fullscreen report, and the environment gotchas: the container build OOM, the Firefox auto-update on ai, and the macOS panel-service wedge that made "Load Temporary Add-on" silently do nothing.
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.
Closes #150. Related to #149 (the blocker) and #148 (the blocked upload).
Session handoff so tomorrow's pickup is clean, plus the probe that closes the Gecko UI gate gap.
HANDOFF_FIREFOX_AMO.mdRecords the state: v1.1.2 tagged, packaged, AMO-clean, credentials verified — and blocked from submission by #149. Carries the root-cause evidence, the one open decision (single branch + port relay +
src/platform.ts, with the churn numbers behind it), the unconfirmed popup fullscreen report, and the environment gotchas.scripts/firefox-smoke.mjs --clickThis is what found #149. It clicks a verdict badge and asserts a visible overlay iframe.
The gap it closes:
addons-linterpassed, all 8 badges rendered, Chrome e2e passed, and the production artifact installed cleanly — while the extension's primary interaction was dead. The only reason we caught it is that M clicked a badge by hand.AUTO_SCAN=true TRUST_DEV_FIXTURES=true bun run build bun run serve:fixtures & node scripts/firefox-smoke.mjs --source-dir dist/firefox --min 5 --clickExpect
OVERLAY VISIBLE: NOand exit 1 until #149 lands.Docs and a test script only — no change to shipped extension code. Wiring
--clickinto CI is deliberately left as follow-up, since the runner choice needs a decision (Firefox onaiauto-updates and could flake).