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.
Reported by a user: a one-page
.odsopens 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.cppwrites each spreadsheet as a<table class="odr-sheet">with one<col>per column carrying the document's own column width as bothwidthandmin-width(translate_table_column_style), and.odr-sheetistable-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
PageViewsetsuseWideViewPortandloadWithOverviewMode, 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
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.printhandswebView.createPrintDocumentAdapter()to the framework with a defaultPrintAttributes, and neither the app nor the core ships any other@media printrule. 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
PdfDocumentAdapter, not the WebView.PaginationSettingis odrcore'stextDocumentMargin, which by its own documentation applies to text documents only.Where a fix could go
Either side, and worth deciding deliberately:
suspendDarkening)..odr-sheeta 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.cppwrites into<thead>. A spreadsheet application does not print those by default, and they add width to a page that has none to spare.