Files
bitvid/artifacts/issue_moderation_tests.md
T
google-labs-jules[bot]andPR0M3TH3AN 756b78e724 fix(nostr): Request all NIP-07 permissions on login
Updated `loginWithExtension` to request `DEFAULT_NIP07_PERMISSION_METHODS` instead of `DEFAULT_NIP07_CORE_METHODS`. This ensures encryption permissions (NIP-04/44) are requested upfront and cached, preventing permission errors or unexpected popups during subsequent operations like DM decryption or preference loading.

Also includes artifacts from TODO triage:
- `artifacts/todos.txt`: Scanned TODOs list.
- `artifacts/issue_moderation_tests.md`: Issue report for moderation test TODOs.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-01-31 01:44:33 +00:00

1.2 KiB

todo: Investigate why visibility check fails in fixture environment

Found TODOs in tests/visual/moderation.spec.ts related to Playwright test failures in headless mode.

Context

Several tests in tests/visual/moderation.spec.ts have commented-out assertions and interactions due to visibility checks failing or clicks timing out when running in the fixture environment (headless).

TODOs

  • // TODO: Investigate why visibility check fails in fixture environment (headless)
  • // TODO: Investigate why click times out in fixture environment (headless)
  • // TODO: Investigate visibility check failure
  • // TODO: Investigate click timeout failure

Code Excerpt

    // TODO: Investigate why visibility check fails in fixture environment (headless)
    // await expect(showAnywayButton).toBeVisible();
    await expect(restoreButtonQuery).toHaveCount(0);

    // TODO: Investigate why click times out in fixture environment (headless)
    // await showAnywayButton.click({ force: true });

Suggested Next Step

Investigate the tests/visual/moderation.spec.ts execution in headless mode. It might be related to rendering timing, fixture loading state, or specific CSS properties affecting visibility in the headless renderer.