Pressing ctrl-shift-u does weirdness.

Mike Hommey mh at glandium.org
Tue Apr 17 18:36:52 UTC 2007


On Tue, Apr 17, 2007 at 10:54:47AM -0700, Phillip Pi <ant at zimage.com> wrote:
> On Tue, Apr 17, 2007 at 07:29:19PM +0200, Mike Hommey wrote:
> 
> > > I don't know if this is a bug or not in IceApe v1.1.1 since I don't 
> > > recall having this problem before v1.1.1. I use Fgupdater.G extension 
> > > (http://www.pierceive.com/) in IceApe v1.1.1. It uses ctrl-shift-u keys 
> > > to call up this extension. However, I noticed this hot key combination 
> > > doesn't work anymore, and IceApe seems to respond weirdly: 1) URL form 
> > > sometimes shows red underlines and 2) I can't type javascript: in it 
> > > (slow and doesn't type the whole letters.
> > 
> > There are two things here:
> > - I guess you installed the Fgupdater.G extension "globally" (as opposed
> >   to in the user profile) which means every upgrade of iceape will break
> >   it. You should install it in the user profile, or if you can't (some
> >   extensions don't support it), save the
> >   /usr/lib/iceape/chrome/installed-chrome.txt file, install the
> >   extension, then compare the new file with the older version, and put
> >   the additional lines in a /var/lib/iceape/chrome.d/99<extensionname>
> >   file. It won't disappear anymore on upgrades
> 
> Hmm, I am pretty sure it is not in global location since I don't see it 
> in my new profile I just made. I cat'ed installed-chrome.txt and don't 
> see anything related to Fgupdater.G extension:

That's totally normal there is nothing related to the extension
anywhere, since the upgrade did erase its traces. You might have
Fgupdater.G files in /usr/share/iceape/chrome and/or
/usr/lib/iceape/components, though. I was just describing what you
should do if you don't want this to happen again.

> Where do I disable this new feature? I did notice this new feature in 
> v1.1.1 compared to older versions like v1.0.8. I already disabled it in 
> IceApe's -> Navigator -> Languages -> Spelling (When typing check my 
> spelling: Never). According to my prefs.js file:
> 
> $ cat prefs.js |grep spell
> user_pref("editor.disable_spell_checker", true);
> user_pref("layout.spellcheckDefault", 0);
> user_pref("mail.spellcheck.inline", false);
> 
> These should be fine, right? Do I assume you pressed ctrl+shift+u and
> then typed javascript: just fine? I forgot to mention that if I hit esc
> key, then the typing problem goes away regardless if fgupdater extension
> is installed or not.

Oh, yes I can reproduce after pressing ctrl+shift+u. Some combinations
of characters produce some arabic-like characters, I guess this somehow
enables another input mode, which must be something gtk does in form
fields, I guess. This just means the Fgupdater.G is not catching the key
stroke anymore, since it's not active.

Mike




More information about the pkg-mozilla-maintainers mailing list