any news??? any beta or something?
On Nov 14, 11:17 pm, "Atul Varma" <[EMAIL PROTECTED]> wrote:
> Yeah, this is an annoying thing. I talked to Blake Kaplan and found out
> that while XPCOM is backwards-compatible at a binary level, the JS API is
> not--it's only backwards-compatible at a source-code level. That means that
> we need not only a different XPCOM component for each platform, but also a
> different XPCOM component for each version of Firefox.
>
> Yeah, it sucks. So I'm trying to see if we can submit a patch to the
> Mozilla platform for FF 3.1 that makes it so we don't need the nsUbiquity
> component anymore:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=445873#c3
>
> If we're allowed to do this and can get the patch shepherded in time, then
> we'll only need the nsUbiquity component for FF 3.0, and we won't have to
> worry about future versions of Firefox.
>
> - Atul
>
> On Fri, Nov 14, 2008 at 5:16 PM, Abimanyu Raja <[EMAIL PROTECTED]>wrote:
>
> > A few days back, the nsIUbiquity XPCOM component wouldn't work in 3.0. Has
> > this been fixed yet? If not, releasing current Ubiquity as 0.1.3 will screw
> > up on 3.0 but work fine on 3.1b1.
>
> > - Abi
>
> > 2008/11/14 Atul Varma <[EMAIL PROTECTED]>
>
> >> Hmm, I just tried out the latest HG of Ubiquity with the latest FF 3.1
> >> nightly built on Nov 13, with both Ubiquity installed as an XPI and in
> >> developer mode, and both scenarios seem to work fine. So I think all
> >> that's needed is to re-publish the current Ubiquity as 0.1.3, possibly
> >> rolling back any changes that aren't fully finished yet (making a branch
> >> is another alternative).
>
> >> FWIW, I think this was the bug that was causing things to go awry on
> >> 0.1.2 with Firefox 3.1:
>
> >> http://hg.toolness.com/ubiquity-firefox/rev/2cadf5bca4ae
>
> >> - Atul
>
> >> On 11/13/08 8:11 PM, Blair McBride wrote:
> >> > I was the one who asked for this report to be posted here. I've since
> >> > been told that this is a known issue with Firefox 3.1 nightlies. The
> >> > issue was mentioned in the recent meeting we had, and I think Atul
> >> > said he'd look into it ASAP.
>
> >> > So just to clarify: This issue seems to only affect recent nightly
> >> > builds of Firefox 3.1.
>
> >> > - Blair
>
> >> > On Nov 14, 4:12 pm, amau96<[EMAIL PROTECTED]> wrote:
>
> >> >> I have a problem, since version 0.1.2 of ubiquity, with firefox 3.1
> >> >> nightly, ubiquity doesn"t work anymore…
> >> >> when I push alt+space, nothing happen. hum, yes something happen, the
> >> >> cursor of the mouse disappear.
> >> >> I don't have any error in my JS consol
>
> >> >> Extension :
> >> >> adblock plus 0.7.5.5 (liste fr france + easylist)
> >> >> firebug 1.2.1
> >> >> google preview 3.15
> >> >> wordreference translator 1.4.1
>
> >> >> Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2pre)
> >> >> Gecko/20081113 Minefield/3.1b2pre
>
> >> >> Amau
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"ubiquity-firefox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/ubiquity-firefox?hl=en
-~----------~----~----~----~------~----~------~--~---
