fix(mobile): close the debug <script> block (batch122 left it open, breaking the keyboard block)
The perf-diagnostics script tag was never closed, so it merged with the following native/keyboard <script> and threw 'Unexpected token <', disabling the keyboard/safe-area init. Add the missing </script>. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -1165,6 +1165,7 @@ window.__perfProbe=function(label){ try{
|
|||||||
window.bzDbg('slidePerf',{label:label||'', frames:frames.length, maxGapMs:max, jankFrames:over, longtasks:longtasks, gaps:frames.slice(0,40)}); }
|
window.bzDbg('slidePerf',{label:label||'', frames:frames.length, maxGapMs:max, jankFrames:over, longtasks:longtasks, gaps:frames.slice(0,40)}); }
|
||||||
})(last);
|
})(last);
|
||||||
}catch(e){} };
|
}catch(e){} };
|
||||||
|
</script>
|
||||||
<script>
|
<script>
|
||||||
// Native shell tag (iOS/Android). Safe-area insets are handled natively by the @capacitor-community/
|
// Native shell tag (iOS/Android). Safe-area insets are handled natively by the @capacitor-community/
|
||||||
// safe-area plugin (it makes env(safe-area-inset-*) report real values), so there's no JS status-bar
|
// safe-area plugin (it makes env(safe-area-inset-*) report real values), so there's no JS status-bar
|
||||||
|
|||||||
Reference in New Issue
Block a user