Skip to content

CANON-041: fix investor-admin access-denied screen — 100vh → 100dvh#41

Open
VaultSparkStudios wants to merge 1 commit into
mainfrom
routine/canon-041-investor-admin-dvh
Open

CANON-041: fix investor-admin access-denied screen — 100vh → 100dvh#41
VaultSparkStudios wants to merge 1 commit into
mainfrom
routine/canon-041-investor-admin-dvh

Conversation

@VaultSparkStudios

Copy link
Copy Markdown
Owner

What

Single-line CANON-041 fix in assets/investor-admin.js: the access-denied fallback screen used min-height:100vh (layout viewport, static) as an inline style. On iOS Safari, 100vh includes the area behind the browser toolbar, so the centered "Access denied" message could be pushed above the visible viewport fold when the chrome is visible. Replaced with min-height:100dvh which tracks the dynamic (visual) viewport.

File changed: assets/investor-admin.js:408

Context

This was the last remaining 100vh usage in the codebase not already covered by an open PR. All other CANON-041 issues found during this audit (nav-sheet 60vh, command palette 100vh, studio-hub sidebar, investor portal mobile nav) already have dedicated open PRs in review.

How to verify on mobile

  1. Load the investor admin page as a non-admin user on iPhone (iOS Safari) — the "Access denied" screen should appear fully within the visible viewport with no overflow, both when the address bar is shown and after it collapses.
  2. Confirm the centered content (message + return link) is always visible and not clipped by the browser toolbar.

🤖 Routine CANON-041 audit — automated PR, do not merge without founder review.


Generated by Claude Code

The access-denied fallback screen rendered via investor-admin.js used
`min-height:100vh` (layout viewport, static) as an inline style. On
iOS Safari, 100vh includes the area behind the browser toolbar, so
the screen slightly overflows the visual viewport when the chrome
is visible. Swapping to `min-height:100dvh` anchors to the dynamic
viewport which tracks what is actually visible to the user.
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.

2 participants