Skip to content

fix: stabilize miniapp foreground/background activation - #402

Merged
Gaubee merged 1 commit into
mainfrom
fix/miniapp-runtime-state-machine-foreground
Feb 6, 2026
Merged

Gaubee merged 1 commit into
mainfrom
fix/miniapp-runtime-state-machine-foreground

Conversation

@Gaubee

@Gaubee Gaubee commented Feb 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • refactor miniapp runtime into fsm* state transitions and domBind* bindings
  • keep background miniapps mounted in DOM (no iframe teardown), use visibility + interactivity control only
  • simplify stack view to shadcn item list and wire activation/minimize behavior
  • fix activation to enforce single-foreground by set intersection/difference and bump target z-order
  • add runtime/container/stack-view tests including activation regression coverage

Validation

  • pnpm check
  • pnpm -s vitest run src/services/miniapp-runtime/__tests__/activate-app.test.ts src/services/miniapp-runtime/__tests__/runtime-state-machine.test.ts src/services/miniapp-runtime/__tests__/container.test.ts src/components/ecosystem/miniapp-stack-view.test.tsx

@Gaubee
Gaubee merged commit 84157ab into main Feb 6, 2026
5 checks passed
@Gaubee
Gaubee deleted the fix/miniapp-runtime-state-machine-foreground branch February 6, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant