Description: Acivation/Tab order is not exported in the correct order from a Writer document to pdf. After setting the Activation order and ensuring the order is correct for all text fields and checkboxes, the order changes after exporting to pdf. I attach a writer document and the corresponding pdf to demonstrate. Steps to Reproduce: 1. Create writer document with text fields and check boxes in random order. 2. Set activation order. 3. Export as pdf. 4. Open pdf and check tab/activation order. Actual Results: Tab order is changed. Expected Results: Tab order should not change. Reproducible: Always User Profile Reset: Yes Additional Info: Tab or Activation Order is not mentioned in Help.
Created attachment 167341 [details] odt file example
Created attachment 167342 [details] pdf file example
I've tried to reproduce the problem, but I couldn't. I can't see a difference between odt-file and pdf-file. To be honest, stp 2 "Set activation order" is not clear to me. Tested with Version: 7.1.0.0.alpha1+ (x64) Build ID: 10b23330a9655658e6d7ef1d008a3302a15e9629 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded
The forms do look very similar, but behave differently. When you fill in a form you click in the first field and enter some data. Then you use the <tab> key to move to the next field. It is usually called the 'Tab Order' in other applications, but LO call it 'Activation Order'. The Tb Order can be adjusted from a button on the Controls Toolbar. It is the 15th from the left, with a blue top. When check boxes are set between text fields the designed order is not followed. I am experimenting and may go back to an earlier version of LO.
Try tabbing through the odf and then through the pdf/fdf forms. The cursor will take a different route.
I just imported the pdf file into the online pdffiller and MasterPDFEditor tools and it worked correctly. It seems to be a problem with Xreader in Linux Mint 20.04. I'll report that.
Per https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status it's not fixed but NOTaBug .
Or, if you confirm it's Xreader issue then it's NotOurBug.