Device: iPad Pro 12.9-inch (5th generation)

OS Version: iPadOS 26.3 (23D127)

App Version: Textastic 10.9.2

Accessibility Feature: Voice Control (hands-free use)

Summary:

Voice Control fails to correctly deliver text input to Textastic's terminal view. This issue has persisted across two iPadOS updates, first observed on January 25, 2026, and remains unresolved as of iPadOS 26.3 (installed February 21, 2026) with Textastic 10.9.2.

Symptom:

Voice Control appears to be active and recognizing commands (as confirmed by testing in standard text fields like Notes), but no text is delivered to Textastic's terminal input field.

Root Cause Analysis:

The issue appears to stem from a conflict between the iPadOS Predictive Text / Composition Engine and how the terminal view handles input:

- When Voice Control processes speech, iPadOS inserts tentative (composition/draft) text into the input field.

- iPadOS then commits the final text, replacing the draft.

- The terminal view does not correctly handle this new two-phase input process, resulting in no visible text being delivered.

Steps to Reproduce:

1. Enable Voice Control via Settings > Accessibility > Voice Control.

2. Open Textastic and launch a terminal session (e.g., via SSH).

3. Use a voice command to dictate a terminal command.

4. Observe that text does not appear in the terminal input field despite Voice Control confirming recognition.

Expected Behavior:

Dictated text and Voice Control aliases should be inserted cleanly into the terminal input field, identical to how they work in Textastic's code editor and other standard text fields (e.g., Notes, Safari address bar).

Impact:

This bug renders Textastic's terminal view completely inaccessible for users who rely on Voice Control for hands-free operation.

Additional Notes:

- Standard text fields, including Textastic's own code editor, handle Voice Control input correctly, confirming the issue is specific to the terminal view's interaction with the iPadOS composition engine.

- The issue did not exist prior to the iPadOS update that introduced the behavior on or around January 25, 2026.

Hello. Would you be able to add full support for TOML? It’s a files that is being used more and more to capture configurations as well as low level data and having support would be greatly appreciated 

I use your app to test WebGL2 graphics via the built-in HTML file viewer. Quite often, after minimizing the app and switching to other apps, the WebGL context gets lost and the canvas stops rendering anything (blank/black). Returning to the app does not restore rendering.

Expected behavior

After returning to the app, WebGL2 rendering should recover correctly (or the viewer should automatically restart the renderer) without requiring a full app restart.

Actual behavior

The context is lost and rendering never comes back. The only workaround is fully restarting the app.

Why this matters

A full restart resets the code editing history/undo-redo, so I lose recent edits. This is very disruptive.

Steps to reproduce

1. Open the attached HTML file (WebGL2 canvas) in the built-in HTML viewer.
2. Minimize the app.
3. Open other apps until this app goes into the background and is effectively “suspended”.
4. Return to the app.
5. The canvas shows nothing and rendering does not recover.

Reproducibility

High. It happens frequently for me; with the attached HTML it’s almost 100% reproducible once the app is suspended in the background.

Environment

• Device: iPhone 13 mini
• OS: iOS 17.6
• Mode: built-in HTML viewer
• WebGL: WebGL2

Attachments

• repro.html

  (minimal reproduction)

Additional notes

This looks like a context loss on backgrounding. It may help to handle webglcontextlost / webglcontextrestored and/or recreate the context/resources when the app returns to the foreground, so the viewer can recover without requiring an app restart.

Would you consider adding Typst language support for Textastic? It would be awesome!

https://typst.app

It’s very difficult to see the icons when using the triple-finger tap gesture on iPhone with iOS 26 due to dark icons on dark background. Although paste is fine and some of the other options are currently disabled due to not having text selected, it’s still nearly impossible to see what some of them are, and the undo icon is also very difficult to see.