Closed
Bug 157394
Opened 24 years ago
Closed 24 years ago
*Gdk-WARNING* when creating input fields in non-en_US locales
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: lkemmel, Assigned: jdunn)
References
Details
(Keywords: fixedOEM, intl)
Attachments
(1 file, 2 obsolete files)
|
3.02 KB,
patch
|
kinmoz
:
review+
kinmoz
:
superreview+
|
Details | Diff | Splinter Review |
When creating input fields in non-US (e.g. iw_IL) locale, "Gdk-WARNING **: can
not create input context with specified input style" error message is displayed
in the shell window.
As a result, X Input Method doesn't start, and mozilla doesn't accept
international input.
| Reporter | ||
Comment 1•24 years ago
|
||
Degrade the IM style, so that input context can be created.
Comment 2•24 years ago
|
||
Lina: is this bug Bidi specific? (i see #ifdef IBMBIDI)
Simon: is IBMBIDI on by default and are you familiar with AIX input method?
Comment 3•24 years ago
|
||
>Lina: is this bug Bidi specific? (i see #ifdef IBMBIDI)
Sorry, I should have checked for other bug before making a comment here.
I see bug 157397 which indicates it is not a bidi specific.
| Reporter | ||
Comment 4•24 years ago
|
||
Roy: Sorry about the late reply and thanks for the clarification. Of course, I
had to mention explicitly that this bug is not bidi specific..
| Reporter | ||
Comment 5•24 years ago
|
||
The previous fix set IM editing style named "root window", which supposed
creating a separate window for pre-edited text.
The current fix suggests querying the system for the styles supported by the
current IM server and then choosing one of them (actually it falls on
"over-the-spot" style).
Another changes in this fix:
- remove IBMBIDI ifdef;
- change AIX4_3 to _AIX ifdef.
Comment 6•24 years ago
|
||
Lina: do you want us to review your code or is not ready yet?
Comment 7•24 years ago
|
||
Lina is on vacation for the next few weeks, but I believe the latest fix is
ready to be reviewed. Thanks.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 8•24 years ago
|
||
Comment on attachment 92570 [details] [diff] [review]
Another fix for the bug
/r=yokoyama
I am not very familiar w/ AIX platform; but the
code looks clean. I will
give /r here; but we should ask kin or Pinkerton for /sr.
lina/philip: do you have a checkin privilage? If you don't, then I can checkin
for you.
Attachment #92570 -
Flags: review+
Comment 9•24 years ago
|
||
Neither of us have checkin privileges at this time. I have asked for
privileges, but am still waiting for approval. I would appreciate you checking
this fix in for us.
Comment 10•24 years ago
|
||
Comment on attachment 92570 [details] [diff] [review]
Another fix for the bug
Isn't this:
+ if ((curr_style & best_style) == curr_style) {
the same as:
+ if (best_style == curr_style) {
or were you trying to see if all of best_style was supported in a give
curr_style:
+ if ((curr_style & best_style) == best_style) {
The rest of the code looks ok, though I really dislike the fact that we are
leaving unreachable code active, doesn't the AIX compiler complain about this?
+ return gIMStyle;
+#endif // _AIX
+
nsCOMPtr<nsIPref> prefs(do_GetService(kPrefServiceCID, &rv));
if (NS_SUCCEEDED(rv) && (prefs)) {
char *input_style;
| Assignee | ||
Comment 11•24 years ago
|
||
removing "branchOEM+", till patch gets r=/sr= for trunk
Whiteboard: branchOEM+ → branchOEM
Comment 12•24 years ago
|
||
+ if ((curr_style & best_style) == curr_style) {
This line is not the same as either of your suggestions. I believe the above
line simply wants to ensure that the current style doesn't contain any styles
which are not allowed. (best_style is a combination of all allowed styles)
Regarding the following line:
+ return gIMStyle;
+#endif // _AIX
+
The AIX compiler does not complain with leaving unreachable code. HP-UX has a
similar workaround above which returns early. I could submit a new patch which
add ifdef/elif/else sections to separate out the platform specific code if you
would find that to be an improvement over the current patch.
Comment 13•24 years ago
|
||
Comment on attachment 92570 [details] [diff] [review]
Another fix for the bug
>This line is not the same as either of your suggestions. I believe the above
>line simply wants to ensure that the current style doesn't contain any styles
>which are not allowed. (best_style is a combination of all allowed styles)
Ok, thanks for the clarification. Add a comment before the |if| check, that
states what you said above, and you got an sr=kin@netscape.com.
As for the unreachable code, it's not a big deal, hopefully your compiler will
optimize out the code after the return. I was just expressing my dislike of
leaving code in that will never execute.
Attachment #92570 -
Flags: superreview+
Comment 14•24 years ago
|
||
Updated•24 years ago
|
Attachment #91276 -
Attachment is obsolete: true
| Assignee | ||
Comment 15•24 years ago
|
||
Roy with your's and kin's reviews, do you plan
to check this into the trunk? Or do you want me
too?
Whiteboard: branchOEM → branchOEM+
Comment 16•24 years ago
|
||
Comment on attachment 96183 [details] [diff] [review]
Same patch - added comment
I think the comment that was added is missing the keyword "only":
+ // Ensure that curr_style contains allowed styles
Attachment #96183 -
Flags: superreview+
Attachment #96183 -
Flags: review+
Comment 17•24 years ago
|
||
You're right. The comment should read "Ensure that curr_style only contains
allowed styles". This change should be made when the fix is checked in.
| Assignee | ||
Comment 19•24 years ago
|
||
fix checked into trunk
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 20•24 years ago
|
||
Lina or someone else:
Could you please verify with the latest build to see if it is still
reproducible? since we don't have AIX here. Thanks!
Comment 21•24 years ago
|
||
Lina is back on Monday ...
I do not see the Gdk Warning anymore with the latest fix. It works fine for me.
Comment 22•24 years ago
|
||
Mark bug as VERIFIED. Please reopen if it is still reproducible.
Status: RESOLVED → VERIFIED
Updated•23 years ago
|
Attachment #92570 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•