Bug 160001 - Exporting PDF via macro with AllowDuplicateFieldNames = true does not have effect
Summary: Exporting PDF via macro with AllowDuplicateFieldNames = true does not have ef...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro
  Show dependency treegraph
 
Reported: 2024-03-02 18:57 UTC by antoniocaroppos
Modified: 2024-11-12 06:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description antoniocaroppos 2024-03-02 18:57:11 UTC
Description:
Exporting as PDF via dialog with the option AllowDuplicateFieldNames enabled results in a PDF where for example 2 textfields which have the same name are connected: If the user types into textfield 1, the text is (at focus loss) shown in textfield 2.

Exporting as PDF with the same option via a macro results in a PDF where these 2 textfields are not connected.

Steps to Reproduce:
1. Create a new document in Writer
2. Add 2 textfields, give each one the same name, for example "firstname".
3. Start the macro recorder
4. Export as PDF via file dialog with the option "Allow duplicate field names" enabled. For your convience, enable "Show PDF after creation."
5. Stop the macro recorder and save your macro as "PDFFromDialog".
6. In the PDF, type into one of the textfields and click into the other textfield. You will see how your text has been transferred to the other textfield.
7. Close the PDF and delete the file.
8. Run the macro.
9. In the newly created PDF, type into textfield 1 and click into textfield 2.
10. Notice how the text is not transferred to textfield 2.


Actual Results:
Macro does not create the same PDF as with File Dialog.

Expected Results:
Macro should create the same PDF


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL threaded
Comment 1 antoniocaroppos 2024-03-02 21:04:12 UTC
Same issue in this version:

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL threaded
Comment 2 Vladimir Sokolinskiy 2024-03-03 12:52:19 UTC
Repro.

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: threaded
Comment 3 Andreas Heinisch 2024-11-12 06:49:01 UTC
You may provide a sample document including the corresponding macro? This provides faster testing for users interested in this bug. Thank you very much!