Skip to content

Fix: add the keyboard resize setting only where Safari will not log it - #530

Merged
SandObserver merged 1 commit into
mainfrom
fix/viewport-keyboard-setting
Oct 20, 2026
Merged

SandObserver merged 1 commit into
mainfrom
fix/viewport-keyboard-setting

Conversation

@SandObserver

Copy link
Copy Markdown
Owner

Summary

  • Remove interactive-widget=resizes-content from the dashboard's viewport meta tag.
  • Append it from ui/js/dashboard.js when GestureEvent is not defined, so Safari's engine never sees the key and Chromium keeps resizing the page for the on-screen keyboard.
  • Point the spotlight test at the script instead of the page.

Testing
All green. Updated 1 test; checked the viewport content in WebKit (no key) and Chromium (key added).

Changelog

Fixed

  • Safari no longer logs a viewport warning when the dashboard loads.

Checklist

  • Stays within the project constraints: one container, no runtime dependencies, no build step (see CONTRIBUTING.md).
  • Tests added or updated for new logic, and the full suite, lint, and typechecks pass.
  • Docs updated if behavior or configuration changed.

@SandObserver SandObserver added the bug Something isn't working label Oct 20, 2026
Safari does not know the interactive-widget viewport key and logs an error
for it on every dashboard load. The dashboard now adds it only on engines
without GestureEvent, so other browsers keep the search sheet above the
on-screen keyboard.
@SandObserver
SandObserver force-pushed the fix/viewport-keyboard-setting branch from 4a4148b to 06cb414 Compare October 20, 2026 21:42
@SandObserver
SandObserver merged commit 0696740 into main Oct 20, 2026
6 checks passed
@SandObserver
SandObserver deleted the fix/viewport-keyboard-setting branch October 20, 2026 21:49
stackyard-release Bot pushed a commit that referenced this pull request Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant