SCIENTIFIC-LINUX-USERS Archives

October 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Fri, 26 Oct 2007 10:56:21 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (77 lines)
Troy Dawson wrote:
> Troy Dawson wrote:
>> Frank, Schluenzen wrote:
>>> Hi Stephan,
>>>
>>>>
>>>> since the update to firefox-1.5.0.12-0.7.SL3, we observe problems 
>>>> with positioning the cursor in text input boxes, like the one for 
>>>> the URL, the search engine, and also widgets embeeded in web pages: 
>>>> Neither the mouse nor the cursor keys can be used to position the 
>>>> cursor anywhere except at the very beginning or the very end of the 
>>>> string.
>>>>
>>>> firefox-1.5.0.12-0.7.slc3 has the same problem.
>>>>
>>>> Could someone confirm that they're seeing this as well? Any ideas 
>>>> how to work around this?
>>>>
>>>
>>> yup, I see the same problem. Actually, it's still possible to move 
>>> around
>>> within the text boxes with mouse and/or cursor - just the pointer (|) 
>>> doesn't
>>> update the position (which is just as bad) ...
>>>
>>> The firefox-1.5-pango-cursor-position-more.patch apparently doesn't 
>>> work properly under SL3 (see PS:). After removing the patch from 
>>> firefox-1.5.0.12-0.7.SL3's spec and rebuilding the rpm everything 
>>> seems to work fine .... at least the pointer positions correctly 
>>> within the text boxes...
>>>
>>> I guess there is a good chance that similar patches make their way 
>>> into thunderbird as well !?
>>>
>>> Ciao, Frank.
>>>
>>> PS: After fiddling a bit with the code: the patch introduces 
>>> inRendContext->GetRangeWidth to deduce the (pixel) length of a 
>>> substring within a text-field which is then used to calculate the 
>>> actual position of the pointer within the text field. As it turns 
>>> out, the function always returns the length of the complete string 
>>> rather than that of the substring (whyever) - so that the pointer 
>>> appears to get stuck at the end (or start) of the string. well, 
>>> didn't try to dig any further ....
>>
>> Hi Frank,
>> I *thought* we actually were disabling all pango stuff when we changed 
>> "enable-pango" to "disable-pango".  But it looks like their patch 
>> doesn't honor that setting enough.
>>
>> Troy
> 
> I'm debating.  Should I fix this, or use this as motivation for people 
> to stop using firefox and thunderbird on SL3 and move to seamonkey.
> SL 309 does *not* have firefox or thunderbird.  At some point, people 
> are going to have to transition off firefox and thunderbird to seamonkey 
> is they are going to stay on SL 3.
> Troy
> 

Looking between thunderbird and firefox, I believe the problem isn't with the 
patch, or the disabling pango in the config file, but in firefox's spec file, 
they have a hack, where they link some pango headers over.

What happens if you take those links out of the spec file?

I'm going to try it myself, but since building it takes a long time, I was 
wondering if anyone had already tried it.

Troy

-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________

ATOM RSS1 RSS2