|
Short Description
|
invalid field generated, wrong length
|
|
Entered
|
By:
PeteL
When: 1998-05-13 05:32:17 Build: 1.03.10a
|
|
Categories
|
Type:
Problem
Department: Product
Category:
HTML Generation
|
Description
|
<INPUT TYPE="TEXT"
NAME="F_1831_9"
MAXLENGTH=9 SIZE=2
value="N"
onFocus="this.form.C_POS.value = '1831'">
<INPUT TYPE="TEXT"
NAME="F_1833_7"
MAXLENGTH=7
SIZE=7
onFocus="this.form.C_POS.value = '1833'">
These fields were generated. I have never before seen a field generated with a MAXLENGTH not equal to its SIZE. Also as you can see, these two fields overlap, which should not happen. Somehow, the length on the first field was set incorrectly to 9, when it should have been 2. I will send a hyenalog trace via email.
|
|
|
|
Append
|
By: WindSurfer When: 1998-05-13 11:48:56 New Status:
Pending Customer
|
|
Comment
|
Thanks-- I'll check using the trace to determine what is breaking.
Screensurfer used to take an entry field that wrapped around the end of a row to the next row and split it into multiple fields. This isn't the default behavior anymore, except on unformatted screens. The default now is to take the field and display it as the size it is on the current row, but give it a maxlength & a name that is equal to the total length of the field.
It looks like in certain situations both of these fields are getting generated in the HTML-- the trace will help reproduce.
|
|
|
|
Append
|
By: WindSurfer When: 1998-05-13 11:54:53 New Status:
Pending Customer
|
|
Comment
|
By the way, while this is a pain, the ticket system is HTML-based, so that your entries need to work as HTML-- this makes formatting capabilities nice, but as a side effect makes cut-and-paste of real HTML a pain...
You can see this because if you view this ticket, you don't see your sample trace, since it includes real HTML.
In the future, if you can just do a quick change to all leading left angle brackets to < (ampersand, less than, semicolon), it will prevent the tag from being interpreted as "real" HTML.
thanks!
|
|
|
|
Append
|
By: PeteL When: 1998-05-13 12:34:02 New Status:
Pending IE
|
|
Comment
|
as you'll see in the trace, these fields are on the same line.
(if you see this soon, ticket # 22) is more/most important) - thanks
|
|
|
|
Append
|
By: WindSurfer When: 1998-05-15 11:12:29 New Status:
Pending Customer
|
|
Comment
|
Can you check this with Build 1.3.10, as it is not reproducing with the protocol trace-- I get the screen with one 9 character field on right margin of row 23, and then a 1 character & 2 character field on right margin of row 24--is this the way the screen is supposed to look?
|
|
|
|
Append
|
By: PeteL When: 1998-05-15 12:00:53 New Status:
Pending IE
|
|
Comment
|
the 1.3.10 version that I have (5/14, 6:40am) still splits it into two overlapping fields. It should be a single 9-byte field, so maybe it fixed itself during a rebuild? Do you expect 10b to be ready soon, or later in the afternoon?
|
|
|
|
Append
|
By: WindSurfer When: 1998-05-15 12:15:42 New Status:
Pending Customer
|
|
Comment
|
The latest one is at ftp://ftp.ieinc2.com/pub/surfer/ss1_3_10.zip... please check it out...
|
|
|
|
Append
|
By: WindSurfer When: 1998-05-15 12:17:39 New Status:
Pending Customer
|
|
Comment
|
Actually, can you e-mail a copy of the template that is displaying this screen--I'm just looking at a <TEAREA 1 1 24 80> version of it-- there may be something happening with the interaction of your template and the field generator...
|
|
|
|
Append
|
By: PeteL When: 1998-05-19 09:11:03 New Status:
Pending IE
|
|
Comment
|
template emailed - problem still exists with 3.1.10b
|
|
|
|
Append
|
By: PeteL When: 1998-05-26 08:38:53 New Status:
Closed
|
|
Comment
|
there may still be something a bit unusual with the code generated, but it turns out that I had a "hanging" link defined to end in the middle of the input field, causing the dual field generation. When I corrected that, it generated correctly as 1 9-byte field.
|