@erkamyaman/capacitor-foldable 8.3.0 → 8.3.1

package/README.md

@@ -37,7 +37,7 @@ const { state, hingeOrientation } = await Foldable.getFoldState();
 
 | Platform | Status | Minimum |
 | -------- | ------ | ------- |
-| Android  | Supported | API 24, `compileSdk` 34 |
+| Android  | Supported | API 24, `compileSdk` 36 |
 | iOS      | Size classes everywhere; fold, hinge and bar placement on iPhone Duo with Capacitor 8.5+, Xcode 27.1+ and iOS 27.1+ | iOS 15 |
 | Web      | Stub, returns `flat` | |
 
@@ -53,7 +53,7 @@ Web views already resize with the window, so a responsive layout that pads with
 - **Where iPhone Duo puts native bars**, so your HTML tab bar can follow. For Ionic's `ion-tabs` there's a ready-made stylesheet, plus a fix for the tab bar disappearing when you fold.
 - **The outer display on Android foldables**: rear display and dual screen.
 
-Google's [adaptive app quality guidelines](https://developer.android.com/develop/adaptive-apps/quality-guidelines/adaptive-app-quality) put window size classes and posture support in Tier 1, and Apple's [iPhone Duo guidance](https://developer.apple.com/design/human-interface-guidelines/designing-for-iphone-duo) asks for layouts that adapt to the fold rather than to a device. This plugin reports what both checklists are about.
+Google's [adaptive app quality guidelines](https://developer.android.com/develop/adaptive-apps/quality-guidelines/adaptive-app-quality) make posture support a Tier 1 check and size-class-driven layouts a Tier 2 one, and Apple's [iPhone Duo guidance](https://developer.apple.com/design/human-interface-guidelines/designing-for-iphone-duo) asks for layouts that adapt to the fold rather than to a device. This plugin reports what both are about.
 
 ## Installation
 
@@ -127,11 +127,11 @@ Using Ionic's `ion-tabs`? `import '@erkamyaman/capacitor-foldable/ionic-tabs.css
 
 ## Store review
 
-The plugin is built so it cannot be the reason an app is rejected.
+The plugin is built to give store review nothing to object to.
 
-**iOS.** Public APIs only, UIKit and Capacitor, with no dynamic lookup or private symbols. It touches none of Apple's [required reason APIs](https://developer.apple.com/documentation/bundleresources/privacy-manifest-files), collects nothing and tracks nobody, and it ships a `PrivacyInfo.xcprivacy` saying exactly that, which Xcode folds into your app's privacy report. Nothing it uses needs a purpose string in `Info.plist`. The iOS 27.1 code is behind a compile-time SDK check, so older Xcode versions build fine.
+**iOS.** Public APIs only, UIKit and Capacitor, with no dynamic lookup or private symbols. It touches none of Apple's [required reason APIs](https://developer.apple.com/documentation/bundleresources/describing-use-of-required-reason-api), collects nothing and tracks nobody, and it ships a `PrivacyInfo.xcprivacy` saying exactly that, which Xcode folds into your app's privacy report. Nothing it uses needs a purpose string in `Info.plist`. The iOS 27.1 code is behind a compile-time SDK check, so any Xcode that Capacitor 8 supports builds fine.
 
-**Android.** The plugin's manifest is empty: it adds no permissions to your app. The hinge angle comes from `TYPE_HINGE_ANGLE`, which needs no permission, and it is registered at `SENSOR_DELAY_NORMAL`, well under the rate that would require `HIGH_SAMPLING_RATE_SENSORS`. Rear display and dual screen go through Jetpack WindowManager's `WindowAreaController`, also permission free. `minSdk` is 24 and `targetSdk` follows your project, so it never holds you back from Play's target API rules.
+**Android.** The plugin adds no permissions and no `uses-feature` to your app, so it changes nothing about which devices can install it. Its own manifest is empty; Jetpack WindowManager merges two optional `<uses-library>` entries, which are how it binds to the OEM window extensions and filter nothing. The hinge angle comes from `TYPE_HINGE_ANGLE`, which needs no permission, and rear display and dual screen go through `WindowAreaController`, also permission free. `minSdk` is 24, the same as Capacitor's own default, and `targetSdk` follows your project.
 
 **Data safety and privacy labels.** Everything stays on the device: the plugin has no network code and stores nothing. There is no entry for it to add to Play's Data safety form or to your App Store privacy label.
 

package/android/src/main/kotlin/io/github/erkamyaman/foldable/DisplayModes.kt

@@ -3,6 +3,7 @@ package io.github.erkamyaman.foldable
 import android.app.Activity
 import android.content.Context
 import android.view.View
+import android.webkit.WebView
 import androidx.core.content.ContextCompat
 import androidx.window.area.WindowAreaCapability
 import androidx.window.area.WindowAreaController
@@ -31,6 +32,7 @@ class DisplayModes(private val activity: Activity) {
     private var rearDisplayArea: WindowAreaInfo? = null
     private var rearDisplaySession: WindowAreaSession? = null
     private var dualScreenSession: WindowAreaSessionPresenter? = null
+    private var dualScreenContent: WebView? = null
 
     fun statuses(): Flow<DisplayModeStatuses> =
         controller.windowAreaInfos
@@ -72,7 +74,7 @@ class DisplayModes(private val activity: Activity) {
 
     fun startDualScreen(createContent: (Context) -> View, onStarted: () -> Unit, onEnded: (Throwable?) -> Unit) {
         dualScreenSession?.let { session ->
-            session.setContentView(createContent(session.context))
+            replaceContent(session, createContent)
             onStarted()
             return
         }
@@ -86,11 +88,12 @@ class DisplayModes(private val activity: Activity) {
             object : WindowAreaPresentationSessionCallback {
                 override fun onSessionStarted(session: WindowAreaSessionPresenter) {
                     dualScreenSession = session
-                    session.setContentView(createContent(session.context))
+                    replaceContent(session, createContent)
                     onStarted()
                 }
 
                 override fun onSessionEnded(t: Throwable?) {
+                    destroyContent()
                     dualScreenSession = null
                     onEnded(t)
                 }
@@ -101,10 +104,27 @@ class DisplayModes(private val activity: Activity) {
     }
 
     fun stopDualScreen() {
+        destroyContent()
         dualScreenSession?.close()
         dualScreenSession = null
     }
 
+    /** A web view left alive keeps its timers and connections running. */
+    private fun replaceContent(session: WindowAreaSessionPresenter, createContent: (Context) -> View) {
+        destroyContent()
+        val content = createContent(session.context)
+        dualScreenContent = content as? WebView
+        session.setContentView(content)
+    }
+
+    private fun destroyContent() {
+        dualScreenContent?.apply {
+            loadUrl("about:blank")
+            destroy()
+        }
+        dualScreenContent = null
+    }
+
     private fun statusOf(area: WindowAreaInfo?, operation: WindowAreaCapability.Operation): String =
         when (area?.getCapability(operation)?.status) {
             WindowAreaCapability.Status.WINDOW_AREA_STATUS_ACTIVE -> "active"

package/android/src/main/kotlin/io/github/erkamyaman/foldable/FoldablePlugin.kt

@@ -216,13 +216,15 @@ class FoldablePlugin : Plugin() {
     @PluginMethod
     fun startDualScreen(call: PluginCall) {
         val url = call.getString("url") ?: return call.reject("url is required.")
+        val target = resolveUrl(url)
+            ?: return call.reject("url must be a page in this app, or a data: URL you built yourself.")
         val displayModes = this.displayModes ?: return call.unavailable("Dual-screen mode needs an activity.")
 
         scope.launch {
             when (lastDisplayModes?.dualScreen) {
                 "available", "active" -> {
                     val settle = Settle(call, "Dual-screen mode")
-                    displayModes.startDualScreen({ context -> dualScreenWebView(context, url) }, settle::started, settle::ended)
+                    displayModes.startDualScreen({ context -> dualScreenWebView(context, target) }, settle::started, settle::ended)
                 }
                 else -> call.unavailable("Dual-screen mode is not available on this device right now.")
             }
@@ -294,12 +296,32 @@ class FoldablePlugin : Plugin() {
         webViewClient = object : WebViewClient() {
             override fun shouldInterceptRequest(view: WebView, request: WebResourceRequest): WebResourceResponse? =
                 bridge.localServer.shouldInterceptRequest(request)
+
+            override fun shouldOverrideUrlLoading(view: WebView, request: WebResourceRequest): Boolean =
+                !isAppUrl(request.url.toString())
         }
-        loadUrl(resolveUrl(url))
+        loadUrl(url)
+    }
+
+    /**
+     * The page on the other display shares the app's web view profile, so it is
+     * kept to the app's own origin: anything else is refused rather than loaded.
+     */
+    private fun resolveUrl(url: String): String? {
+        if (url.startsWith("//")) return null
+
+        val scheme = Uri.parse(url).scheme
+        if (scheme == null) return URL(URL(bridge.appUrl), url).toString().takeIf(::isAppUrl)
+        if (!scheme.equals("http", true) && !scheme.equals("https", true) && scheme != "data") return null
+
+        return url.takeIf { scheme == "data" || isAppUrl(it) }
     }
 
-    private fun resolveUrl(url: String): String =
-        if (Uri.parse(url).scheme != null) url else URL(URL(bridge.appUrl), url).toString()
+    private fun isAppUrl(url: String): Boolean {
+        val app = Uri.parse(bridge.appUrl)
+        val target = Uri.parse(url)
+        return target.scheme == app.scheme && target.host == app.host && target.port == app.port
+    }
 
     private inner class Settle(private val call: PluginCall, private val mode: String) {
         private var settled = false

package/ionic-tabs-ios26.css

@@ -52,3 +52,12 @@ html.ios:not(.vertical-bars-leading):not(.vertical-bars-trailing) ion-tab-button
     background: rgba(255, 255, 255, 0.1);
   }
 }
+
+@media (prefers-reduced-transparency: reduce), (prefers-contrast: more), (forced-colors: active) {
+  html.ios ion-tab-bar {
+    background: Canvas;
+    -webkit-backdrop-filter: none;
+    backdrop-filter: none;
+    border: 1px solid CanvasText;
+  }
+}

package/ionic-tabs.css

@@ -4,7 +4,7 @@
   bottom: var(--vertical-tab-bar-bottom, 24px);
   z-index: 10;
   flex-direction: column;
-  width: 45px;
+  width: 52px;
   height: auto;
   padding: 3px 2px;
   border: none;
@@ -13,6 +13,7 @@
   background: rgba(255, 255, 255, 0.78);
   -webkit-backdrop-filter: blur(12px) saturate(180%);
   backdrop-filter: blur(12px) saturate(180%);
+  --color-selected: #0071e3;
   box-shadow:
     inset 0 0 0 0.5px rgba(0, 0, 0, 0.2),
     inset 0 0 8px rgba(0, 0, 0, 0.04),
@@ -37,14 +38,27 @@
   --padding-end: 0;
   flex: 0 0 auto;
   width: 100%;
+  min-width: 44px;
   max-width: none;
   height: 54px;
+  min-height: 48px;
   border-radius: 22px;
 }
 
+/* Hidden to the eye, still there for VoiceOver and TalkBack: `display: none`
+   would take the tab's name out of the accessibility tree. */
 .vertical-bars-leading ion-tab-button ion-label,
 .vertical-bars-trailing ion-tab-button ion-label {
-  display: none;
+  position: absolute;
+  width: 1px;
+  height: 1px;
+  margin: -1px;
+  padding: 0;
+  border: 0;
+  overflow: hidden;
+  clip: rect(0 0 0 0);
+  clip-path: inset(50%);
+  white-space: nowrap;
 }
 
 .vertical-bars-leading ion-tab-button.tab-selected,
@@ -85,3 +99,15 @@ ion-tab-bar[hidden] {
     background: rgba(255, 255, 255, 0.1);
   }
 }
+
+/* Reduced transparency, higher contrast, forced colours: drop the blur and
+   give the pill an opaque background so the icons stay legible. */
+@media (prefers-reduced-transparency: reduce), (prefers-contrast: more), (forced-colors: active) {
+  .vertical-bars-leading ion-tab-bar,
+  .vertical-bars-trailing ion-tab-bar {
+    background: Canvas;
+    -webkit-backdrop-filter: none;
+    backdrop-filter: none;
+    border: 1px solid CanvasText;
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@erkamyaman/capacitor-foldable",
-  "version": "8.3.0",
+  "version": "8.3.1",
   "description": "Fold-state and dual-display APIs for foldable devices in Capacitor apps",
   "main": "dist/plugin.cjs.js",
   "module": "dist/esm/index.js",

package/skills/capacitor-foldable/SKILL.md

@@ -6,6 +6,7 @@ metadata:
   author: erkamyaman
   version: '0.1'
   status: beta
+  checked: 2026-09, against Xcode 27.1, Capacitor 8.5, Play target API 36
 ---
 
 # Capacitor Foldable
@@ -21,7 +22,7 @@ npm install @erkamyaman/capacitor-foldable
 npx cap sync
 ```
 
-Capacitor 8 uses the current major. Capacitor 7 apps install `@erkamyaman/capacitor-foldable@7`, which reports the fold on Android and size classes everywhere, but has no iPhone Duo support: a Capacitor 7 app built with Xcode 27 crashes at launch, because iOS 27 needs the scene lifecycle that Capacitor 8.5 and later adopted. The 7.x line also predates the `--fold-*` variables (8.1.0) and the Ionic tab stylesheets, so the CSS below needs Capacitor 8.
+Capacitor 8 uses the current major. **If you are on Capacitor 7 and building with Xcode 27, upgrade to 8.5 or later before anything else**: those apps crash at launch, because iOS 27 needs the scene lifecycle that only 8.5 adopted, and a crash on launch is an automatic App Review rejection. Capacitor 7 apps can install `@erkamyaman/capacitor-foldable@7` and build with Xcode 26, which reports the fold on Android and size classes everywhere but has no iPhone Duo support. That route closes when Apple requires the iOS 27 SDK in April 2027. The 7.x line also predates the `--fold-*` variables (8.1.0) and the Ionic tab stylesheets, so the CSS below needs Capacitor 8.
 
 ## Start here: CSS before JavaScript
 
@@ -84,4 +85,4 @@ npm run build      # or the app's build
 npx cap sync
 ```
 
-Then run it open flat, half open and closed, and fold it shut and open again, which suspends and resumes the web view on iOS. On iPhone Duo the posture picks the display, so that covers both screens; on Android the outer display needs rear display mode. [testing.md](references/testing.md) has the commands.
+Then run it open flat, half open and closed, and fold it shut and open again, which suspends and resumes the web view on iOS. Do one pass at the largest system text size and one with VoiceOver or TalkBack on, since a layout that splits at the crease is exactly where reading order and target sizes go wrong. On iPhone Duo the posture picks the display, so that covers both screens; on Android the outer display needs rear display mode. [testing.md](references/testing.md) has the commands.

package/skills/capacitor-foldable/references/android.md

@@ -33,9 +33,11 @@ await Foldable.startDualScreen({ url: 'cover.html' });
 await Foldable.stopDualScreen();
 ```
 
-The URL is loaded in a second web view on the other display, and a relative path resolves against the app's own URL, so the page has to be part of the web build. A `data:` URL is often easier for dynamic content, and is what the plugin's own example app uses.
+**Load only content you control.** The plugin refuses anything that is not a page of your own app or a `data:` URL, and keeps the second web view on your origin once it is loaded, because that view shares the app's cookies and storage. Never pass a URL that came from a server, a deep link, a push payload or a user.
 
-Treat it as a presentation surface: a plain web view with no Capacitor bridge, so no plugin API inside it. Anything it needs goes in the URL, though the page is served through the app's own local server, so same-origin storage is readable there too. Calling `startDualScreen` again rebuilds the page rather than messaging it.
+A `data:` URL is the easier route for dynamic content and is what the plugin's own example uses, but note two things. It gets an **opaque origin**, so `localStorage` and friends throw there and it cannot read the app's storage: put what the page needs into the document. And `encodeURIComponent` is URL encoding, not HTML escaping, so interpolating a name or a message into `data:text/html,...` is an injection into a page that has JavaScript on. Escape it for HTML first, or ship a static page and pass values in the fragment for its own script to insert with `textContent`.
+
+Treat it as a presentation surface: a plain web view with no Capacitor bridge, so no plugin API inside it. Calling `startDualScreen` again replaces the page rather than messaging it.
 
 Both modes share one window area behind the scenes, and both stop when the activity goes away.
 

package/skills/capacitor-foldable/references/api.md

@@ -107,6 +107,8 @@ await Foldable.stopDualScreen();
 
 `startRearDisplay()` shows a system confirmation first, and `startDualScreen()` rejects outright without a `url`. Both accept `available` or `active`.
 
-`displayModeChange` reports both modes together. Relative URLs resolve against the app's own URL, so `cover.html` has to be a page you ship in the web build, which for a bundler means adding it as an extra entry point. A `data:` URL works too, and is the easier route for dynamic content. That page runs in its own web view with no access to Capacitor plugins, and calling `startDualScreen` again replaces it.
+`displayModeChange` reports both modes together. Relative URLs resolve against the app's own URL, so `cover.html` has to be a page you ship in the web build, which for a bundler means adding it as an extra entry point. A `data:` URL works too, and is the easier route for dynamic content.
+
+The page must be content you wrote: the plugin rejects any other origin, and `encodeURIComponent` is URL encoding rather than HTML escaping, so escape anything you interpolate into a `data:text/html` document. See [android.md](android.md). That page runs in its own web view with no access to Capacitor plugins, and calling `startDualScreen` again replaces it.
 
 Android only; both read as `unsupported` on iOS and web, where the `start` methods reject. See [android.md](android.md).

package/skills/capacitor-foldable/references/css-layout.md

@@ -118,6 +118,24 @@ const handle = await Foldable.addListener('foldStateChange', apply);
 
 `animation-play-state` is not inherited and only affects elements that carry a CSS animation, so put it on the animated element itself. For a chart or anything driven by JavaScript, listen to `foldingChange` and stop redrawing instead. The class appears as the hinge starts moving and goes half a second after it stops, and only on devices that report a hinge angle: an Android foldable without a hinge sensor never gets it.
 
+## Accessibility
+
+The crease is exactly where reading order and target sizes go wrong, so four rules:
+
+- **Keep source order equal to visual order.** The `nth-child` pinning above works only while it is. Re-order the markup rather than moving things visually, or a screen reader reads the pages in the wrong sequence.
+- **Name each page and let the keyboard reach it.** Both panes scroll independently, so give them `role="region"` with an `aria-label`, and `tabindex="0"` on the scroll container.
+- **Use `rem` for your own gutters and insets**, not pixels. Android scales web view text with the system font size while iOS does not unless you opt in, so fixed pixel padding drifts in one direction and never moves in the other. Grid items pinned to a fixed track also need `min-width: 0`, or long words push them into the crease.
+- **Targets stay at least 44 pt, or 48 dp on Android**, which matters most for anything sitting beside the fold.
+
+`prefers-reduced-motion` is a separate concern from `.folding`: the class is a device signal that comes and goes with the hinge, so honour the media query independently, and use `animation: none` there rather than pausing on an arbitrary frame.
+
+Right to left needs its own arm, because the fold variables are physical viewport coordinates while `:first-child` is not:
+
+```css
+[dir='rtl'] .fold-vertical .reader .page:first-child { left: calc(var(--fold-left) + var(--fold-width)); right: 0; width: auto; }
+[dir='rtl'] .fold-vertical .reader .page:last-child { left: 0; width: var(--fold-left); }
+```
+
 ## What not to do
 
 - Splitting at `50%`. The coordinates are relative to the web view, and on iPhone Duo the band has width.

package/skills/capacitor-foldable/references/ionic.md

@@ -45,6 +45,10 @@ readonly mode = signal<'game' | 'meter'>('game');
 
 If you do route, `provideIonicAngular({ animated: false })` removes the slide, but be aware it disables every Ionic animation app-wide, including modals and ripples.
 
+## Apple's rules for the side bar
+
+The vertical bar has an order: primary navigation at the top, then prominent actions. Apple also asks you to prefer a symbol over text there, since anything with a label stays in a horizontal bar. The stylesheet hides the labels visually for that reason but keeps them for VoiceOver, so leave them in your markup.
+
 ## Styling gotcha
 
 `ion-tab-bar` ships `contain: strict`, which brings size containment with it. The moment you let either dimension come from its contents, it lays out as if empty and collapses: height in the side pill, width in the iOS 26 variant. Both shipped stylesheets set `contain: none` for that reason.

package/skills/capacitor-foldable/references/testing.md

@@ -2,7 +2,7 @@
 
 ## iPhone Duo simulator
 
-Needs the iOS 27.1 runtime, which the device type refuses to go below, and Xcode 27.1 to build against the 27.1 SDK. Build against the 27.0 SDK and the app fills more of the inner display but still leaves gaps; build against anything older and it runs in compatibility mode inside a black border with no fold reported. The iOS 27.2 beta runtime does not run iPhone Duo at all, as observed on this beta. In Xcode 27 the simulator lives inside **DeviceHub.app**, not `Simulator.app`.
+Needs the iOS 27.1 runtime, which the device type refuses to go below, and Xcode 27.1 to build against the 27.1 SDK. Build against the 27.0 SDK and the app fills more of the inner display but still leaves gaps; build against anything older and it runs in compatibility mode inside a black border with no fold reported. In Xcode 27 the simulator lives inside **DeviceHub.app**, not `Simulator.app`.
 
 ```bash
 open "$(dirname "$(xcode-select -p)")/Applications/DeviceHub.app"