dtourolle
c55ff45692
The bottom nav rendered under the Android navigation bar, and full-screen
playback controls spilled into unusable screen edges. It looked device-specific
(Motorola bad, Fairphone fine) but every device was equally unpadded — only the
intrusion differed: a tall opaque 3-button bar swallows the nav, a thin
translucent gesture pill overlaps harmlessly.
None of the app's safe-area handling was ever active, for two independent
reasons:
1. app.html had no `viewport-fit=cover`, so every `env(safe-area-inset-*)`
resolved to 0px — the padding in app.css and BottomUi was a no-op.
2. Android WebView maps only the *display cutout* into `env()`; the status bar
and navigation bar are never reported. With enableEdgeToEdge() and
targetSdk 36 (enforced from 35, opt-out ignored from 36) the WebView always
spans them, so CSS could not learn about them by any route.
WindowInsetsBridge now reads `systemBars() | displayCutout()` and publishes
`--jt-inset-*` CSS custom properties, both pushed on every inset change
(rotation, nav-mode switch, PiP) and pullable via `AndroidInsets.get()` — the
pull is required because the first inset pass lands before the document exists
and a page load wipes the pushed inline style. app.css folds them with `env()`
via `max()` into `--safe-*`, the only thing components may pad from.
Exactly one element owns each edge: the shell takes top/left/right, BottomUi
takes bottom (inside its surface box, so the colour extends behind the gesture
bar), and shellReservesBottomInset hands bottom back to the shell on routes with
no bottom UI. The full-screen players inset their control layers only, leaving
video and artwork edge-to-edge.
The theme's `fitsSystemWindows=true` claimed the opposite of what actually
happened — overridden at runtime, ignored at this target SDK — and is removed.
Also converts six nested `h-screen`/`min-h-screen` boxes to `h-full`: the shell
is `h-screen` *and* inset-padded, so its content box is `100vh - safe-top` and
any nested 100vh box overflows by exactly the inset (the library column would
have clipped its own BottomUi). A test guards against reintroduction.
26 lines
1.1 KiB
Prolog
26 lines
1.1 KiB
Prolog
# JellyTau custom keep rules.
|
|
#
|
|
# These classes are loaded by name from the Rust backend via JNI
|
|
# (env.find_class / class-loader lookups), so R8 cannot see the
|
|
# references and would otherwise strip or rename them in a minified
|
|
# release build — causing an instant ClassNotFoundException crash on
|
|
# startup. See src-tauri/src/player/android/mod.rs and
|
|
# src-tauri/src/credentials.rs.
|
|
-keep class com.dtourolle.jellytau.player.** { *; }
|
|
-keep class com.dtourolle.jellytau.security.** { *; }
|
|
|
|
# Picture-in-picture is driven from the WebView through an
|
|
# @JavascriptInterface bridge, so the only references to these methods live
|
|
# in JavaScript. R8 sees them as unused and would strip them, silently
|
|
# breaking the PiP button in release builds only.
|
|
-keep class com.dtourolle.jellytau.PictureInPictureManager { *; }
|
|
-keep class com.dtourolle.jellytau.VideoOverlayManager { *; }
|
|
-keep class com.dtourolle.jellytau.WindowInsetsBridge { *; }
|
|
-keepclassmembers class * {
|
|
@android.webkit.JavascriptInterface <methods>;
|
|
}
|
|
|
|
# Media3 / ExoPlayer is accessed reflectively in places; keep it intact.
|
|
-keep class androidx.media3.** { *; }
|
|
-dontwarn androidx.media3.**
|