Issue 3018 - Allow form-Fields to Expand and Contract Dynamically
Summary: Allow form-Fields to Expand and Contract Dynamically
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: 641
Hardware: All All
: P4 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: rfe_eval_ok, usability
Depends on:
Reported: 2002-02-07 15:29 UTC by ggalt
Modified: 2013-08-07 14:38 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description ggalt 2002-02-07 15:29:48 UTC
Currently, fields that a user places in a document (to be filled in later by a 
database or another user) are static in length.  This means that when data is 
inserted in a field that is either longer or shorter than the static field 
length, the information is either truncated (in the printout), or white space 
is left at the end of the field.  This results in unprofessional documents and 
prevents the use of fields for creating forms that can be filled in later by 
other users (especially if the document is locked to prevent the user from 
changing important aspects of the document, such a contract language).

The fields should expand and contract dynamically, and even wrap around to the 
next line if the input is long enough.  This would allow, for example, the 
legal department to create a contract form with blanks for price, date, and 
name and address of contracting party, that a salesperson could fill in later.  
If the document is locked (and preferably the lock is password protected), the 
salesperson could not change any of the legal language, but could still 
generate a contract that looked professional.

FYI, this is the way that MS Word currently works with fields and it can be 
quite useful.
Comment 1 stx123 2002-02-08 18:08:47 UTC
moving to component "wordprocessor"
Comment 2 stx123 2002-02-14 00:22:56 UTC
Reassign issue to owner of selected subcomponent
Comment 3 stefan.baltzer 2002-05-24 10:18:59 UTC
George: I hope you are familiar with sections. They might be helpful 
for the scenarios you described (they can be set to read only, have 
PW protection, be hidden with conditions, have dynamic content...).
Reassigned to Christian.
Comment 4 christian.jansen 2003-02-10 12:32:08 UTC
Reassigned to Bettina.
Comment 5 bettina.haberer 2003-07-14 11:34:54 UTC
Changed target milestone.
Comment 6 bettina.haberer 2003-10-24 10:51:22 UTC
This issue is considered for 'Office later' as it is not part of a
keyfeature (PCD) for 'Q'.
Comment 7 2004-09-14 11:23:41 UTC
reassigning & adding keywords according to new RFE process - sophie
Comment 8 lohmaier 2004-09-17 01:32:55 UTC
? Should be possible in current builds. Please check again.
Comment 9 2004-09-17 09:24:52 UTC
Hi Christian, 
May be I'm wrong, but from what I've checked in m51, you can add scrollbars to a
field or input multiline text, but the field itself is still static. It can't
expand or contract dinamically. Sophie
Comment 10 lohmaier 2004-10-25 21:10:01 UTC
I think we're talking about different "fields" then.
It took me a while until I realized that this issue is about form-elements. ->
extending summary.

Database fields work as expected, Input fields work as expected.

As mentioned before, you probably don't need to stick with form fields, there
are other possibilities in Writer...