Closed Bug 81749 Opened 24 years ago Closed 24 years ago

localIM does not work on FORM field

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Platform:
Sun
Solaris
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: blackconnect, Assigned: prabhat.hegde)

References

Details

For example, it is possible to input russian letters in the field "Web (URL) location", but it is impossible in the text fields of web forms inside html-pages. Russian letters may be printed in the "Subject:" filed of Mail Composer, but cann't be printed in the mail body window, etc ....
Changing QA contact to katakai@japan.sun.com, please re-assign further as appropriate.
QA Contact: andreasb → katakai
masaki - Can you look at this? BTW, this seems to work in my trunk latest, Solaris9 builds. prabhat.
Hi Prabhat, I understand this bug is still existing. Will you try the input on HTML form field? Yes, on URL field filed, it works but doesn't work on FORM. I'll work on this next week.
Status: NEW → ASSIGNED
Prabhat, I changed the summary. localIM does not work on FORM field. Actually it works on URL field and other UI filed. After the some debug, it seems that no native char is not passed on any FORM field. Prabhat, can you ask Toshi and Sriram about localeIM and this problem? ON URL FIELD, handle_key_press_event call InitKeyEvent call InitKeyPressEvent anEvent.charCode = 0 anEvent.keyCode = 0 Key Press event: gtk string = '?', keyval = '' = 0, --> keyCode = 0x0, char code = '' Commit ON FORM FIELD, handle_key_press_event call InitKeyEvent call InitKeyPressEvent anEvent.charCode = 6d Key Press event: gtk string = 'm', keyval = 'm' = 109, --> keyCode = 0x0, char code = 'm' OnKey
Summary: russian letters input does not work on Solaris → localIM does not work on FORM field
This has been turned out to be Xlib's bug on Solaris.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
*** Bug 110344 has been marked as a duplicate of this bug. ***
Verified. Need to apply Solaris patch.
Status: RESOLVED → VERIFIED
Can anyone post the bugid in SunSolve and the patchid/rev which fixes this (S2.7/S2.8), please ?
The Solaris 8 patch that solves this problem is 108773, at least revision -13 (current revision is -14). There is no patch for Solaris 7.
Is there a fix for Solaris 2.7 in work or would a backport to S2.7 require a customer escalation ?
AFAIK there's no patch for Solaris 7 in the works, maybe someone else knows. If not, a customer escalation is probably needed.
You need to log in before you can comment on or make changes to this bug.