IC84115: DBCS: HATS V 8.0.2 FIELD LENGTH CHECKING WITH CHROME NOT WORKING AS EXPECTED.

Rational Host Access Transformation Services Fix Pack 5 (8.0.0.5) for 8.0
Rational Host Access Transformation Services Fix Pack 3 (8.0.0.3) for 8.0
Rational Host Access Transformation Services Fix Pack 1 (8.5.0.1) for 8.5
Rational Host Access Transformation Services Fix Pack 2 (8.5.0.2) for 8.5
Rational Host Access Transformation Services Fix Pack 3 (8.5.0.3) for 8.5
Rational Host Access Transformation Services Fix Pack 4 (8.0.0.4) for 8.0
Rational Host Access Transformation Services Fix Pack 4 (8.5.0.4) for 8.5
Rational Host Access Transformation Services Fix Pack 5 (8.5.0.5) for 8.5

APAR status

• Closed as program error.

Error description

• ENVIRONMENT:
  Hats 8.0.0.2
  
  5250 session
  OS: Win XP
  RAD V8.0.4
  WAS V8.0
  Google Chrome V19.0.1084.52
  
  User reported to be on the above environment. User is aware that
  per documentation HATS supports Google's Chrome browser. On this
  environment user noted that the behaviour of exceeded characters
  on an Open/ Mix field differs from other HATS supported
  browsers. When the user inputs exceeded characters on a 5250
  Open field, HATS does not trim the characters after IME
  committing. If it is 5250 J field ( ei, DBCS only field), the
  problem does not occur.
  User tested HATS field widget and text input widget and in this
  case the problem does occur.  User expects field length checking
  using Chrome browser to work the same as the Firefox and IE
  browsers.
  
  
  Example / recreate:
  
  On Chrome:
  Field Type: 5250 Open Field
  Filed length: 20 Bytes
  This means only 9 DBCS characters are allowed.
  (9*2 + 2(for SO/SI) = 20)
  
  Initial data: "
  Input data using IME: "             "
  
  Commit the IME, but exceeded characters still remains
  
  Press the "Tab" key to move the cursor to the next field; the
  cursor does not move. Instead, it focuses the field. At the same
  time, exceeded characters are trimmed.
  
  Press the "Tab" key again, but the cursor still remains in the
  same field.
  
  Press the "Tab" key again, and this time, the cursor moves to
  the next field.
  
  
  On Firefox:
  Field Type: 5250 Open Field
  Filed length: 20 Bytes
  This means only 9 DBCS characters are allowed.
  (9*2 + 2(for SO/SI) = 20)
  
  Initial data: "        "
  Input data using IME: "        "
  
  Press the "Tab" key, and the cursor moves to the next field.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Customers who use Chrome browser with DBCS   *
  *                 codepage.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When user inputs exceeded               *
  *                      characters on a 5250 Open(Mix) field    *
  *                      in Chrome, then submit characters       *
  *                      from IME,                               *
  *                      the field length checking is not        *
  *                      working.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  User presses enter key to submit characters from IME, but
  Chrome does not pass the enter key code from the key event,
  so field length checking process was not triggered.
  

Problem conclusion

• Chrome will trigger textinput event when submit characters
  from IME, use this event with IME state to check and run the
  field length checking process for Chrome.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL HATS FOR 5

• Fixed component ID

  5724U6800

Applicable component levels

• R800 PSY

     UP