MozGest 2.1 will be ready soon.
http://www.mousegestures.org/websvn/listing.php?repname=MozGest&path=%2Fmozgest_2_1_branch%2F
http://www.mousegestures.org/svn/mozgest_2_1_branch
( u: guest pw: mozgest )
** Summary changed:
- Update Mozgest to 2.0.3
+ Update Mozgest to 2.1.x
--
Update Mozgest
1.)
The Mouse Gestures extension only changes the context menu behaviour from
mousedown to mouseup
for context menus inside the "content" where Mouse Gestures is working. In all
other places the menu
will be shown on mousedown! (Like the context menu for tabs or toolbars)
2.)
I don't think the p
Let me guess:
"Nightly Tester Tools" were used to force compatibility of "Mouse Gestures
1.5.2" with Fx3?
This bug was reported BEFORE MozGest (1.9) was available as a working package.
So I think this bug is invalid.
-> https://bugs.launchpad.net/ubuntu/+source/mozgest/+bug/218363
--
Right cli
> please post it to the mailing list as it is not a bug.
Ok, actually there is no one willing to give an answer.
Please close this bug.
** Changed in: firefox-3.0 (Ubuntu)
Assignee: irfan khan soomro (mozilla-firefox3) => (unassigned)
Status: Confirmed => Invalid
--
[HARDY] binary c
Public bug reported:
Binary package hint: mozgest
http://www.mousegestures.org/svn/mozgest_2_0_branch
** Affects: mozgest (Ubuntu)
Importance: Undecided
Status: New
--
Update Mozgest to 2.0.3
https://bugs.launchpad.net/bugs/276705
You received this bug notification because you ar
or:
http://www.mousegestures.org/websvn/listing.php?repname=MozGest&path=%2Fmozgest_2_0_branch%2F
--
Update Mozgest to 2.0.3
https://bugs.launchpad.net/bugs/276705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
After installing libnspr4-dev (4.7.1+1.9-0Ubuntu0.8.04.1) binary
components are loaded.
--
[HARDY] binary components provided by extensions not loaded
https://bugs.launchpad.net/bugs/217812
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just done a fresh Ubuntu 8.04.1 installation. After installing all
distro-updates and
starting Fx 3.0.1 and installing an extension with a binary component, the
component
was _not_ loaded.
After installing libnspr4-dev and deleting compreg.dat and xpti.dat from the Fx
profile the
component
Just tried to install the google toolbar.
Same problem. The binary components are not registered.
Install the toolbar and have a look at the error console...
Is this still minor?
And from my point of view it is totally out of perspective to ask for it as
"licensed as free".
Fx3 provided by Ubunt
To summarize:
Some extensions don't work under Ubuntu 8.04 because mozilla links
against old libc libraries.
Is there a documentation about that somewhere?
Is there a documentation available HOW to compile binary components working
with
Fx2, Fx3/Mozilla and Fx3/Ubuntu?
Is there a Mozilla-SDK a
I've just installed the update for libnspr4-0d
(4.7.1+1.9-ubuntu0.8.04.5) and everything is working fine now.
It might be necessary to delete compreg.dat and xpti.dat from the used
Fx profile to (re)register the component(s).
--
[HARDY] binary components provided by extensions not loaded
https:/
I've made an extension for testing. Its main goal is to dump a message to the
console about "ghost commands".
(To see the messages you have to set "browser.dom.window.dump.enabled" to
"true" and start Fx from the console)
As a side effect the extension tries to hack around the bug. Please note th
Well, before 3.1 isn't released I don't see a reason why I should test 3.2.
"Performance" can't be the only problem here...
Alexander Sack schrieb:
> I cannot easily trigger this on my machine with the recent firefox-3.2
> dailies in
> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive
>
Warning!
The following STR might be another bug or total rubbish.
STR:
1. Bring up a context menu over the content
2. Move your mouse to highlight a menu entry (don't click, don't move)
3. Press "ESC"
4. Do a "fast" right click to bring up the context menu again
5. The highlighted entry will fire
Alexander Sack schrieb:
> Right ... thats the current understanding. Also I somehow have the
> feeling that this happens because the focus gets auto moved to the
> none-existing popup. The randomness could be explained by a overflow
> given that the actual popup size is still zero.
Extending my "te
Public bug reported:
Binary package hint: mozilla-firefox
Hardy beta.
Binary components (.so) within extensions are not loaded at startup with Fxb5.
Instead this message is shown in the error console:
Failed to load XPCOM component: //.so
Additionaly this error is reported after EVERY e
** Changed in: firefox-3.0 (Ubuntu)
Sourcepackagename: firefox => firefox-3.0
--
[HARDY] binary components provided by extensions not loaded
https://bugs.launchpad.net/bugs/217812
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
17 matches
Mail list logo
