NS_COMPOSITION_QUERY does not return the same value for height per line

RESOLVED FIXED in mozilla1.9.3a4

Status

()

Core
Editor
P3
normal
RESOLVED FIXED
17 years ago
8 years ago

People

(Reporter: Masaki Katakai, Assigned: masayuki)

Tracking

({inputmethod, intl})

Trunk
mozilla1.9.3a4
x86
Linux
inputmethod, intl
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [behavior])

Attachments

(2 attachments)

(Reporter)

Description

17 years ago
NS_COMPOSITION_QUERY is used to get the position and width,
height of current composition. Linux/UNIX nsWidget uses
this interface to get the position and height. The height
will be used for the height of composition text in
over-the-spot mode, which is the mode that XIM server draws
the composition text.

nsWidget::UpdateICSpot()
{
   compEvent.message = NS_COMPOSITION_QUERY;
   compEvent.eventStructType = NS_COMPOSITION_QUERY;
   compEvent.compositionMessage = NS_COMPOSITION_QUERY;

   this->OnComposition(compEvent);

   spot.x = compEvent.theReply.mCursorPosition.x;
   spot.y = compEvent.theReply.mCursorPosition.y +
                compEvent.theReply.mCursorPosition.height;
   SetXICBaseFontSize( compEvent.theReply.mCursorPosition.height - 1);
}

However, it seems that the height is changed even when
the cursor is in the same line. For example, when the cursor
is in "Subject" field,

cursor is in the beginning of the field, height is returned as 16 on
my environment,

	x=85 y=199 h=16

It seems that 16 point is correct.

But if you type one character, the value of height is changed to
19 from 16.

	x=149 y=198 h=19

It seems that 19 point is bigger that expected.

Please look at the snapshots. You can not find the problem that
the size of composition text is not same even when we're trying
to enter characters in the Subject field.
(Reporter)

Comment 1

17 years ago
Created attachment 33370 [details]
drawing composed text in 16 point
(Reporter)

Comment 2

17 years ago
Created attachment 33371 [details]
but wrong height is returned, so drawing in 19 point

Comment 3

17 years ago
Changing QA contact to ftang@netscape.com for now.
QA Contact: andreasb → ftang

Comment 4

17 years ago
Katakai san, should this be assigned to widget or editor? It doesn't look like
an i18n bug.

(Reporter)

Comment 5

17 years ago
Hi Hotta-san, yes, can you move this to editor compoment?

Comment 6

17 years ago
Change component to editor and reassign.
Assignee: nhotta → beppe
Component: Internationalization → Editor
Keywords: intl

Comment 7

17 years ago
assign to anthonyd
Assignee: beppe → anthonyd
Priority: -- → P3
Target Milestone: --- → mozilla0.9.2

Updated

17 years ago
Whiteboard: [behavior]

Comment 8

17 years ago
andreas, I don't understand why you assign this QA contact to me. This bug can 
be seen by the user/tester. reassign the qa contact back to andreas

I don't think this should be an moz0.9.2 bug. The current behavior is not good 
but it is still good enough for a product. katakai- is that ok?
QA Contact: ftang → andreasb

Comment 9

17 years ago
had a mail exchange with ftang, we agreed this can go to 1.0
Target Milestone: mozilla0.9.2 → mozilla1.0
(Reporter)

Comment 10

17 years ago
OK.

This is a problem when we use over-the-spot mode, which is not
the default input style. The default is on-the-spot. But some
users in japanese prefer over-the-spot. Anyway, target should be 1.0.

Thanks.

Comment 11

17 years ago
Changing QA contact to ylong@netscape.com
QA Contact: andreasb → ylong

Comment 12

17 years ago
--> kin
Assignee: anthonyd → kin

Comment 13

16 years ago
Bulk move of mozilla1.0 bugs to mozilla.1.0.1. I will try to pull some of these
back in if I can.
Target Milestone: mozilla1.0 → mozilla1.0.1

Updated

16 years ago
Target Milestone: mozilla1.0.1 → Future
QA Contact: amyy → editor
Assignee: kinmoz → nobody
Keywords: inputmethod
should be fixed by bug 528435 and bug 520732.
Assignee: nobody → masayuki
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Depends on: 520732, 528435
Resolution: --- → FIXED
Target Milestone: Future → mozilla1.9.3a4
You need to log in before you can comment on or make changes to this bug.