Bug 53359 - : Formatting: Writer should not extend table colums to size of database field name in form letters
Summary: : Formatting: Writer should not extend table colums to size of database field...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-10 21:41 UTC by vimr
Modified: 2014-07-08 17:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of current behaviour (202.39 KB, image/jpeg)
2012-08-10 21:41 UTC, vimr
Details
screenshot of expected behaviour (180.33 KB, image/png)
2012-08-10 21:43 UTC, vimr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vimr 2012-08-10 21:41:25 UTC
Created attachment 65409 [details]
screenshot of current behaviour

Problem description: 
When creating form letters from database where column names are long and descriptive, writer expands the columns and rows of table to make the names visible.

The problem is, that all other stuff after the table will be displaced, it is moved backwards. But its not like "What you see is what you get". The form letter will not look like i designed it. It makes hard to create such form letters.


Current behavior:
See attached screen shot (CurrentBehaviour.jpg).

Expected behavior:
Do it like in the spreadsheet (see screen shot spreadsheet.jpg). The spreadsheet does not expand the column or the row, it shows a little red triangle to show that there is a long name.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Comment 1 vimr 2012-08-10 21:43:33 UTC
Created attachment 65410 [details]
screenshot of expected behaviour
Comment 2 A (Andy) 2013-02-16 16:16:20 UTC
I don't think, that this is a bug.  But, one can think about such a possible enhancement to force this behavior.
Comment 3 retired 2013-11-23 18:33:08 UTC
vimr: Is this bug still valid / reproducible with the latest LO release?  Currently 4.1.3.2: http://www.libreoffice.org/download/

Could you please attach the document in question? That would help speed up the process of confirming and successively fixing this bug a lot. A step-by-step description of how to reproduce the issue is most helpful and will help to speed up the processing of this problem a lot.

Setting to NEEDINFO until more detail is provided.

After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Comment 4 QA Administrators 2014-06-01 21:30:26 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-07-08 17:18:13 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO