Skip to content

armgit / bento

Public Imported from GitHub
0

Bento, the office suite that fits in a file

Present: never switch to Reveal's scroll view

nyblnet26908bcd1c3f
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 281984d4..8a9cc7f2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,11 @@ pre-1.0.
## [Unreleased]
+- **Fix: presenting on a phone shows the deck, not a scrollable page.** Below
+ about 435px wide, the presentation was quietly switching to a scrolling
+ reading layout instead of a slideshow — so swipe navigation stopped working
+ and hidden interactive slides became scrollable content.
+
- **Fix: presenting was broken.** Slides showed at a fraction of the screen
with speaker notes spilling underneath. A stray missing bracket in the
stylesheet swallowed all of the presentation layout rules. Nothing was wrong
diff --git a/slides/src/present.ts b/slides/src/present.ts
index 42fcfdca..7006b351 100644
--- a/slides/src/present.ts
+++ b/slides/src/present.ts
@@ -149,6 +149,27 @@ export function startPresentation(
// for tiny embeds.
minScale: 0.1,
maxScale: 100,
+ /**
+ * Never switch to Reveal's SCROLL VIEW, whatever the window size.
+ *
+ * Reveal 5 auto-swaps the classic one-slide-at-a-time renderer for a
+ * vertical scrolling page below `scrollActivationWidth`, default 435px.
+ * That default is meant for a deck embedded in an article, where reading
+ * beats presenting. Presenting is the only thing this overlay does, and
+ * EVERY phone is under the threshold — an iPhone is 390-430 CSS px — so
+ * the platform bento/tray exists to serve would silently get a different
+ * renderer from a laptop.
+ *
+ * The concrete cost is navigation, not layout: measured at 402px the
+ * section still scales and positions correctly. But scroll view replaces
+ * slide navigation with page scrolling, which bypasses our own swipe
+ * handling (Reveal's is off deliberately — it walks into hidden state
+ * slides), and turns those state slides into scrollable content when they
+ * are supposed to be reachable only through a link. It also renders every
+ * section at once rather than one at a time, which is the opposite of what
+ * a presentation overlay is for.
+ */
+ scrollActivationWidth: 0,
center: false,
hash: false,
history: false,