[BUG]: Duplicate fullscreen event causes double updates

[Dushyantcoder07]

SUMMARY:

Duplicate fullscreenchange listener and deprecated base64 helpers in page.tsx cause double fullscreen state updates and unsafe share-link encoding (Unicode problems).

Steps to reproduce:

1. Open the app (home page).
2. Toggle fullscreen (via header button or the command).
3. Observe duplicate state updates/flicker or unexpected behavior.
4. (Optional) Create a share link with non‑ASCII text and try to load it.

Expected:

Single fullscreen state update per enter/exit; share links encode/decode UTF‑8 reliably.

Actual:

Two identical fullscreenchange handlers are registered so the state update runs twice (can cause UI flicker, double renders, or stale state). Base64 helpers use escape /unescape which are deprecated and can corrupt Unicode in shared code.

[Dushyantcoder07]

Please assing this issue to me under GSSoC'26 @Debmallya-03

[Kokila-chandrakar]

Hi @Debmallya-03

I would like to work on this issue under GSSoC 2026.

I reviewed the issue and understood that duplicate fullscreenchange listeners in page.tsx are causing multiple fullscreen state updates, which may lead to flickering, unnecessary re-renders, or inconsistent UI behavior.

I also noticed the deprecated escape/unescape base64 helpers being used for share-link encoding, which can break Unicode/non-ASCII text handling.

My planned approach is to:

• Remove duplicate fullscreenchange event listeners and ensure only a single stable listener manages fullscreen state updates
• Refactor the share-link encoding/decoding logic to use modern UTF-8 safe methods
• Verify fullscreen toggling behavior across enter/exit actions
• Test share links with non-ASCII/Unicode text to ensure reliable encoding and decoding
• Keep the implementation lightweight and aligned with the existing code structure

I’ll also test edge cases to ensure no regressions in fullscreen controls or share-link functionality.

Please assign this issue to me. Thank you!