If the on-screen keyboard covers the active line in Collabora Online, first save your changes, dismiss the keyboard, and scroll the document until the caret is visible above it. If the problem returns, open the same file in a full mobile browser; this helps determine whether the cause is the browser, an embedded WebView, or the page that hosts Collabora.
There is no single user setting that fixes every mobile keyboard overlap. Collabora Online runs inside a browser or another product’s integration, so the available remedy depends on which layer is holding the editor at the wrong height. The checks below separate a temporary editing workaround from changes an administrator or app developer may need to make.
This changes the current view rather than correcting the layout. If the caret stays visible only until the next keystroke, or the page jumps when the keyboard opens, continue with the browser and host checks.
Repeat the same editing action with the same file and note where it fails. Collabora describes Collabora Online as a responsive browser editor, and distinguishes it from the separate Collabora Office mobile app. Those paths can use different browser engines, host containers, and keyboard handling, so compare like with like before reporting a product defect.
Collabora’s official FAQ describes responsive Collabora Online use in mobile browsers. Its mobile product overview separately discusses browser-based Collabora Online and the dedicated mobile app. Use that distinction when choosing which team should receive a bug report.
On mobile, the visual viewport is the part of a page currently visible on screen; the keyboard can shrink it without changing the page’s layout viewport. MDN notes that viewport behavior varies among browsers. In an embedded setup, the top-level host page may have useful visual-viewport measurements while the iframe’s own measurements do not represent the keyboard-adjusted screen in the same way.
Check that the host page responds when the keyboard opens: its editor frame should fit the available height, the caret should remain reachable, and the page should be able to scroll the frame into view. Avoid a fixed pixel height or a permanently full-screen frame that assumes the keyboard never changes the visible area. Use the outer page’s viewport resize and scroll events to recompute the space available to the editor, then test on the actual browsers and devices your users rely on. MDN documents the VisualViewport API and its resize events for this kind of visible-area change.
Some browsers also support the viewport setting interactive-widget=resizes-content, which asks the browser to resize page content when the virtual keyboard appears. It affects the host page’s layout and browser support is not uniform, so do not add it as a universal Collabora fix. Test the whole embedded experience, including menus, toolbar, scrolling, and keyboard dismissal, before deploying it. MDN documents this option in its viewport meta reference.
Ask the app developer to inspect the Activity that contains the WebView. Android’s official guidance says android:windowSoftInputMode="adjustResize" resizes the app layout to the space left by the keyboard, keeping content accessible when scrolling is needed. For an app that embeds Collabora, the Activity manifest may include:
<activity
android:name=".EditorActivity"
android:windowSoftInputMode="adjustResize" />The exact Activity name and existing manifest attributes depend on the app; merge this setting into the current declaration rather than adding a duplicate Activity. This Android setting applies to a native Android app or WebView host, not to a normal browser tab and not to iOS. See the Android keyboard visibility guide before changing an app build.
If the web page is controlled by your cloud-storage provider or organization, users may not be able to change its frame sizing. Send the checklist and reproduction details to that service’s administrator; only the owner of the host page or app can change its viewport or WebView configuration.
Troubleshoot a mobile browser keyboard covering text in Collabora Online, with quick workarounds and separate checks for browsers, embedded WebViews, and host pages.
Set print and download limits for ONLYOFFICE links, room members, or Docs API sessions, then verify the restrictions from a recipient account.
Set a backup destination, schedule, Mail coverage, and retention limit in ONLYOFFICE Workspace, then verify the archive is ready to restore.
Start the Enterprise Docker Compose stack, persist its license and data, configure JWT safely, and confirm the editors are ready to integrate.
Use an ONLYOFFICE JavaScript macro to remove nonprinting characters and trim extra spaces from a defined spreadsheet range, with a safe review workflow.
Connect ONLYOFFICE DocSpace to Active Directory or OpenLDAP, import users and groups safely, map account fields, and schedule reliable synchronization.
Move portal data from Disk Default to a supported cloud storage provider, or relocate Docker data safely by changing its host volume mapping.
Identify whether Document Server uses a Linux package or Docker, remove only its components, and check remaining data without deleting shared services by mistake.
Trace slow collaborative editing to Docker resource pressure, proxy connections, or document load, then choose the fix that matches your measurements.
Install custom fonts in ONLYOFFICE Document Server, compare persistent Docker mounts with direct copies, rebuild the font list, and verify the result.
