Bug 142213 - FILESAVE PPTX Animation trigger roundtripped incorrectly
Summary: FILESAVE PPTX Animation trigger roundtripped incorrectly
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx, implementationError
Depends on:
Blocks: PPTX-Animations
  Show dependency treegraph
 
Reported: 2021-05-11 08:58 UTC by NISZ LibreOffice Team
Modified: 2022-03-06 03:32 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from PowerPoint (46.43 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2021-05-11 08:58 UTC, NISZ LibreOffice Team
Details
The original file saved by Impress (31.30 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2021-05-11 08:59 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document in PowerPoint (47.09 KB, image/png)
2021-05-11 08:59 UTC, NISZ LibreOffice Team
Details
Screenshot of the exported document in PowerPoint (52.43 KB, image/png)
2021-05-11 09:00 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2021-05-11 08:58:58 UTC
Created attachment 171869 [details]
Example file from PowerPoint

Attached PPTX file has an animation trigger set on the blue oval shape: its animation starts on clicking the image.
This is opened correctly, and after saving as PPTX and reopening in Impress it seems to be correct.
In PowerPoint however the file behaves incorrectly, the ellipse is no longer seen as set to have the animation start on clicking on the image.

Steps to reproduce:
    1. Open attached file in Impress
    2. Save as PPTX
    3. Open that file in PP
    4. Open the Animations ribbon, then the Animations pane, open the Timing settings of the Ellipse 1

Actual results:
Ellipse is no longer set to be triggered by clicking on the image.

Expected results:
The trigger setting should be retained.

LibreOffice details:
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: d7f734db2c078ced3ce08ad58cd816a79abe3bcf
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

Also happens with 7.0, 6.3.

in 6.2 the trigger setting was not read correctly from the original PPTX file.
Comment 1 NISZ LibreOffice Team 2021-05-11 08:59:31 UTC
Created attachment 171870 [details]
The original file saved by Impress
Comment 2 NISZ LibreOffice Team 2021-05-11 08:59:57 UTC
Created attachment 171871 [details]
Screenshot of the original document in PowerPoint
Comment 3 NISZ LibreOffice Team 2021-05-11 09:00:47 UTC
Created attachment 171872 [details]
Screenshot of the exported document in PowerPoint
Comment 4 Roman Kuznetsov 2021-08-05 13:57:09 UTC
No repro in

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: ac80ec817eb07c77a51bc0729985a473c734182e
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

NISZ team, could you retest it in current master?
Comment 5 QA Administrators 2022-02-03 03:38:49 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2022-03-06 03:32:39 UTC
Dear NISZ LibreOffice Team,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp