Created attachment 114920 [details]
this file contains combinations textboxes with 'no fill', Transparent fill and solid fill.
Steps to Reproduce:
1. Open attached file on latest LO master.
Current behaviour :
Textbox background with 'no fill' are rendered with white background.
Textbox background should be transparent.
@Sushil : I can confirm this with
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Locale : fr_
but why do you think this is a bug ? Did it work differently in previous versions of LibreOffice ? How do you expect it to work ? How does it display in Word ?
'No fill' appears to takes the default document background colour that is set in the Preferences > General > Appearance. This is not the same as transparency.
Setting to NEEDINFO, as I am not quite grasping what the problem is. Perhaps if you could provide details of what you see in Word, and what you expect to see in LibreOffice, we might eb able to move this bug report further.
Created attachment 114944 [details]
This is how MS word renders text-boxes without fill.
Created attachment 114945 [details]
This is how LO writer imported those text boxes.
@Alex Thurgood :
In MS word, Text-boxes with no fill are rendered as transparent text-boxes.
You can see in screen shot, In text-box "text1" and "text2", behind shape color is clearly visible.
But when we open same file on LO writer. It renders those shapes with white background
hence color from from behind shape is not visible.
Reproducible with LO 184.108.40.206, Win 8.1 (also the difference to MSO is reproducible)
For me this is an undesired behaviour if I compare it with MSO. Therefore, I would see it as Status = NEW.
Sushil Shinde committed a patch related to this issue.
It has been pushed to "master":
tdf#90720 Textframe background was not transparent
It will be available in 5.0.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
*** Bug 61766 has been marked as a duplicate of this bug. ***