Closed Bug 375228 Opened 17 years ago Closed 1 month ago

After upgrading to Firefox/2.0.0.3 the hotkey of Ultralingua doesn't pop up translations windows *anymore*

Categories

(Core Graveyard :: Widget: Mac, defect)

1.8 Branch
PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wilmotte, Unassigned)

References

()

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; fr; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; fr; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

With my current 6.03 version of Ultralingua <http//www.ultralingua.com>, since I've been upgrading to Firefox/2.0.0.3, the hotkey of Ultralingua doesn't pop up translations windows *anymore*.
It used to work with previous versions of Firefox.
It is still working with current versions of Excell, FileMaker Pro,...

Reproducible: Always

Steps to Reproduce:
1.Launch Firefox and Ultralingua in any order
2.Put the cursor on any text word in any page shown by Firefox
3.Hit the hotkey set up in the Preferences window of Ultralingua
Actual Results:  
Nothing happens

Expected Results:  
Translations and definitions should appear next to the cursor in a Ultralingua pop-up window, but now with the upgraded Firefox, no window pops up anymore

Pop-up windows are not desabled in my Firefox Preferences
Sounds like this is a problem after the update, rather than the update process itself.
Component: Software Update → General
QA Contact: software.update → general
Version: unspecified → 2.0 Branch
Jean Pierre, can you please try with a new profile? You'll need to reinstall Ultralingua again. See http://kb.mozillazine.org/Profile_Manager
I've created a new profile, then reinstalled Ultralingua, then launched Firefox using the new profile. The problem is still not fixed.
Jean Pierre, which shortcut key have you specified in Ultralingua? There shouldn't have been any hotkey changes in Firefox 2.0.0.3 from 2.0.0.2 that would have caused this. Nick sounds right when he says it was probably something that happened after the update. I'd like to try this out on my machine using the same hotkey, however.

Oh, and what is the last version of Firefox you had that *did* work with Ultralingua?
(In reply to comment #4)
> Jean Pierre, which shortcut key have you specified in Ultralingua?
<F1>

Remember, it's still working with Filmaker, Eudora, Excell,...

> Oh, and what is the last version of Firefox you had that *did* work with
> Ultralingua?

I don't remember.  Sorry.  It was something like 1.x.y.z  Maybe x is 5.  I had downloaded the latest version i've found available in the beginning of september 2006.
Thank Jean Pierre. I can indeed reproduce this with Firefox 2.0.0.3 but not with Firefox 1.5.0.11. I'm not entirely sure how Ultralingua works, so I need to figure that out to see how this broke.
Severity: major → normal
Keywords: regression
(In reply to comment #6)
> Thank Jean Pierre.
It's me, Sam !

>I can indeed reproduce this with Firefox 2.0.0.3 but not
> with Firefox 1.5.0.11.
Great !  ;)

>I'm not entirely sure how Ultralingua works, so I need
>to figure that out to see how this broke.
Ok.  But, no stress, please.
This broke on the branch between the 2006-08-25-03 and 2006-08-26-03. The regression range is http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-08-25+03&maxdate=2006-08-26+03&cvsroot=%2Fcvsroot

I'm still not entirely sure how Ultralingua works, but there was some changes to nsMacEventHandler.cpp which look suspect.

CCing various people, confirming this bug, and sending to Core.
Assignee: nobody → joshmoz
Status: UNCONFIRMED → NEW
Component: General → Widget: Mac
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → mac
Version: 2.0 Branch → 1.8 Branch
Caused by 339346, probably.
Assignee: joshmoz → nobody
Product: Core → Core Graveyard
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.