Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

A spreadsheet prints at its own width, so a wide one is cut off on the right

Offen
  • Stimmt etwas nicht?
#644 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
62/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
css, kotlin
Bereich
frontend, mobile

Rechercherichtung

Start with PrintingManager.print and PageView in the Android app to see how the print job and its PrintAttributes are built, then read document_element.cpp where .odr-sheet and translate_table_column_style fix the table width in centimetres, plus the @media print rule in odrcore's stylesheet that forces zoom:1. Decide whether to scale from the app side (mirroring suspendDarkening) or add a print stylesheet in the shared renderer, and note the <thead> ruler as optional to hide. Done means a wide sheet prints scaled to the page width instead of being clipped, verified through the app's print path or WebView print preview.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

low

Reported by a user: a one-page .ods opens and displays correctly, but printing it from the phone comes out too wide and is cut off along the right edge. The same file prints correctly from a desktop. They were explicit that it is a minor annoyance for them.

Reproduced in the code rather than on paper, but the path is unambiguous.

Why it happens

A sheet is laid out at an absolute width. document_element.cpp writes each spreadsheet as a <table class="odr-sheet"> with one <col> per column carrying the document's own column width as both width and min-width (translate_table_column_style), and .odr-sheet is table-layout:fixed. The table is therefore exactly as wide as the document says, in centimetres, no matter what it is rendered onto.

On screen that is invisible, because PageView sets useWideViewPort and loadWithOverviewMode, so the WebView zooms out until the sheet fits. The core also applies a body zoom of its own.

On paper the zoom is deliberately removed. The core's stylesheet ends with

@media print{:root{--odr-zoom:1!important}body{zoom:1!important}}

commented "paper has its own geometry; beats the script's inline zoom" — which is right as far as it goes, but nothing then fits the sheet to that geometry. PrintingManager.print hands webView.createPrintDocumentAdapter() to the framework with a default PrintAttributes, and neither the app nor the core ships any other @media print rule. So the sheet is rendered at its natural width against the printable page width, and whatever does not fit is clipped.

A desktop office suite scales or paginates a sheet to the paper instead, which is why the same file is fine from a PC.

Scope

  • Spreadsheets, and any other document wider than the page. Text documents are unaffected in practice because they are laid out to a page width already.
  • PDFs are unaffected: they print through PdfDocumentAdapter, not the WebView.
  • The "page margins" toggle cannot help here — PaginationSetting is odrcore's textDocumentMargin, which by its own documentation applies to text documents only.

Where a fix could go

Either side, and worth deciding deliberately:

  • In the app, by asking for a page size that fits the content, or by scaling the WebView for the duration of the print job the way dark mode is already suspended for it (suspendDarkening).
  • In odrcore, by giving .odr-sheet a print stylesheet that scales the sheet down to the page, or breaks it across pages the way a spreadsheet application would.

The second is the more correct fix and helps every frontend, but it is a change to the shared renderer, so it needs its own decision.

Worth noting while in here

The printed page also carries the row and column ruler — the gutter and the A/B/C header row that document_element.cpp writes into <thead>. A spreadsheet application does not print those by default, and they add width to a page that has none to spare.

Vorherrschende Sprache
Kotlin
Sterne
473
Forks
44
Ø Merge
4 Std. 12 Min.
Gemergte PRs (30 T.)
42

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opendocument-app/OpenDocument.droid

Alle Issues in opendocument-app/OpenDocument.droid

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.