0 Fork 0

mirror of https://github.com/PR0M3TH3AN/bitvid.git synced 2026-10-27 16:02:26 +00:00

Files

T

google-labs-jules[bot]andPR0M3TH3AN 106f7640c4 fix(exploreData): trigger refresh immediately on visibility change

- `handleVisibility` only scheduled intervals but didn't trigger an immediate refresh when returning to the tab.
- This caused `tests/unit/services/exploreDataService.test.mjs` to fail (assertion `0 !== 1`).
- Added explicit calls to `refreshWatchHistoryTagCounts` and `refreshTagIdf` when `document.hidden` becomes false.

Co-authored-by: PR0M3TH3AN <[email protected]>

2026-02-18 15:10:29 +00:00

1.2 KiB

Raw Blame History

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.

1.2 KiB Raw Blame History