There was made a change (yesterday?) which renders the textfield component from:
<input class="TxtFld_sun4" id="form1:textField1" name="form1:textField1"
size="20" style="left: 96px; top: 168px; position: absolute; width: 360px"
<span id="form1:textField1" style="left: 288px; top: 192px; position: absolute">
<input class="TxtFld_sun4" id="form1:textField1_field"
name="form1:textField1_field" size="20" type="text" value=""/>
which breaks the resizing, adding the encapsulating span causes the issue.
do you know if this change came from woodstock ?
I just checked the checkin history on the woodstock component. The change was
make in build #4 before opensource. A <span> is always rendered in the
FieldRenderer. Used to be only rendered if there is a label for the component
I think this is a component issue. Since there is a <span> around the TextField
(same problem in TextArea), the width and height on the span do not affect the
size of the text field. The size of the text field is controlled by size
(columns) attribute and the size of the text area is controlled by the
columns/rows. The designer does change the span width and height when you resize
The DropDown, ListBox, PasswordField also have the same problem.
If you decide, the component should not be allowed to be resized in the
designer, then it is easy to do.
If you specify (in the DesignInfo),
RESIZE_CONSTRAINTS = NONE
then designer will not provide any resize handle
Removed the resize handlers at designtime for TextField, TextArea,
PasswordField, DropDown and ListBox since
- For DropDown and ListBox, it does not make sense to resize them anyway.
Without the width set, the browsers will automatically adjust the width to the
longest item. With the width set, the long items can actually get cut off.
- For TextField, TextArea and PasswordField, it makes more sense to change the
"columns"/"rows"(for textarea) attributes to control the width of the components.
- Resizing the height of TextField, TextArea and PasswordField does not make
We need to document this new behavior in release notes. Otherwise, it'll confuse
the old users.
We also need to specifically mention this for projects imported from Creator and
5.5/5.5.1. If the user has resized the above components in the old projects,
then after import the projects into NB6, they might notice the width is not the
same as before. Advise the user to use the columns/rows attributes in the new
Release note added
*** Issue 106840 has been marked as a duplicate of this issue. ***
Verified. This is a functional change. Release note was added.
Documentation has been added.
Do you have any plan to fix this issue in future release?
Japanese community member also encountered this and thinks
to be fixed in future.
No. This will not be fixed.
Just some clarification. The components can be resized by changing the columns/rows.
But they can not be resized by width/height (the old way). It is just a
different way of resizing them. This way should
make more senses because if you resize them using width/height, the last
character/column might only show partially.
Also see desc8 in issue #124393 for CSS workaround to
add width for listbox, dropdown.