Bug 73413 - FILEOPEN: Color gradient in frames are set to black to white after loading file
Summary: FILEOPEN: Color gradient in frames are set to black to white after loading file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 21:36 UTC by Oliver Konz
Modified: 2015-05-07 13:32 UTC (History)
1 user (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 Oliver Konz 2014-01-08 21:36:41 UTC
Problem description: 
Custom color gradients in frames are set to black to white after loading file.

Steps to reproduce:
1. Create a graphic object, i.e. a rectangle, and create a new custom gradient to fill it. Then this object can be deleted.
2. Create a text frame and give it the custom color gradient as background (btw. frame templates cannot contain gradients?).
2. Save the file and close Writer
3. Open the file

Current behavior:
The custom color gradient is replaced with a black to white gradient. You have to reassign the custom gradient to the frame.

Expected behavior:
The custom gradient should be still there.
              
Operating System: Windows 7
Version: 4.1.4.2 release
Comment 1 Jacques Guilleron 2014-01-09 17:07:36 UTC
Hello Oliver,

I reproduce this behavior using LO 4.1.4.2 & Windows 7 Home Premium. Notice that if the first object is not deleted, the frame text will keep the gradient applied.

Kind regards,

Jacques
Comment 2 Joel Madero 2015-05-02 15:41:16 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later)
   https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
 If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Comment 3 Oliver Konz 2015-05-07 13:32:50 UTC
Can no longer reproduce the error in 4.4.2.2 Arch Linux build-1