Bug 78347 - FILESAVE: DOC - Table border color not retained
Summary: FILESAVE: DOC - Table border color not retained
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.6 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOC-Tables
  Show dependency treegraph
 
Reported: 2014-05-06 16:52 UTC by Yousuf Philips (jay) (retired)
Modified: 2017-09-29 19:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
how the table border looked before saving it to doc and after opening it (128.08 KB, image/jpeg)
2014-05-06 16:52 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2014-05-06 16:52:36 UTC
Created attachment 98572 [details]
how the table border looked before saving it to doc and after opening it

I download the .docx file found at < http://download.microsoft.com/documents/uk/partner/publicsector/DraftMicrosoftResponsetoGovernment.docx >, opened it in LibO and then saved it as a .doc file. Then i re-opened it and the table on page 14 did not retain its border color. This was tested on the last releases from 3.6 to 4.2, including 4.2.5, though it is fine in 4.3.
Comment 1 tommy27 2014-05-06 20:28:32 UTC
thanks Jay for spotting out this one too

bug confirmed under Win7x64 using 4.2.3.3

bug fixed in 4.3.0.0.alpha1+
Build ID: a1dd961c3093f5f7624e4d1f2240e9120fd13f23
TinderBox: Win-x86@39, Branch:master, Time: 2014-05-06_11:47:48

status --> WORKSFORME since it's fixed in 4.3.x
Comment 2 Yousuf Philips (jay) (retired) 2014-05-06 20:31:27 UTC
yes it does work in 4.3 as i had already reported, but shouldnt we want it to work in 4.3 as well.
Comment 3 Yousuf Philips (jay) (retired) 2014-05-06 20:32:23 UTC
i meant 4.2. :)
Comment 4 tommy27 2014-05-06 20:38:10 UTC
not every fix can easily be backported to 4.2.x
moreover we don't know the exact committ that fixed it.
anyway there's just a couple of  months before 4.3.0 release.
Comment 5 Yousuf Philips (jay) (retired) 2014-05-06 20:44:27 UTC
but when 4.3 is released, 4.2 becomes the new stable and alot of conservative/enterprise users will be using that build. so in general, should i not be reporting bugs that are fixed in 4.3?
Comment 6 tommy27 2014-05-06 20:51:02 UTC
keep reportig them, I think it's useful for the record to know that a certain bug is fixed in a dev branch.