2026-08-14 - 2026-08-15
Overview
1 Pull request merged by 1 user
Merged
#272 fix: render the view "Back" lands on after the popup is reopened (closes #268)
6 Pull requests proposed by 1 user
Proposed
#282 fix: answer the page when a background handler throws (closes #280)
Proposed
#284 fix: one transaction approval at a time, and honest copy for a nonce collision (closes #271)
Proposed
#286 build: add ESLint to script/lint and containerize linting (closes #152)
Proposed
#288 test: assert the #150 and #151 items the harness did not cover (closes #188)
Proposed
#289 fix: settle a site approval on the port that carries its teardown (closes #275)
Proposed
#291 build: run the browser e2e suites in CI (closes #259)
1 Issue closed from 1 user
Closed
#268 fix: Back after reopening the popup lands on a blank screen, because goBack() never re-renders
4 Issues created by 1 user
Opened
#283 Uniswap V2_SWAP_EXACT_OUT (command 0x09) is decoded by a function nothing calls
Opened
#285 docs: README still documents the EIP-1193 code loss that #274 fixed
Opened
#287 flake: the Chrome e2e dApp signing prompt loses its page about one run in three under load
Opened
#290 test: make test-e2e is flaky under host load — "the extension opened no approval window within 30000ms"
11 Unresolved Conversations
Open
#259
build: nothing automatic ever runs the e2e suites, so every browser-level guarantee is manual-only
Open
#218
test: popup reload mid-refresh can fail the e2e run with "loadHomeTxs failed: Failed to fetch"
Open
#271
fix: two concurrent dApp transactions are populated with the same nonce, and the second fails terminally
Open
#275
fix: approving a site connection races the popup teardown and can be recorded as a rejection
Open
#152
build: add ESLint to script/lint — make check cannot currently catch undefined identifiers
Open
#188
test: assert the DoD items from #150 and #151 that the harness does not yet cover
Open
#190
milestone 1.0.0: approval-path security, build-integrity guard, e2e harness and filter coverage
Open
#281
refactor: one shared extension-API module, and drive the dApp flows on Firefox (closes #153)
Open
#280
fix: a throw inside handleRpc hangs the dApp's promise forever with no error
Open
#153
fix: Firefox target is non-functional — Chrome callback APIs used against the promise-only browser namespace
Open
#229
test: the Settings view has no browser coverage, so a wrong element id takes the whole screen down undetected