Here is a Friday treat: Jetpack 0.8 rc1! Jetpack 0.8 includes the
Toolbar and Places APIs (see their respective JEPs for doc info) As
we stated in previous posts, this will be the final Jetpack release
that is based on the old Jetpack platform, from here on out, we will
be building on the new rebooted platform. Expect a release on this
new platform in about 6 weeks.
Have fun playing with the new toys ;)
https://ubiquity.mozilla.com/jetpack-xpi/jetpack-latest-beta.xpi
- Daniel
> --
> You received this message because you are subscribed to the Google Groups "mozilla-labs-jetpack" group.
> To post to this group, send email to mozilla-la...@googlegroups.com.
> To unsubscribe from this group, send email to mozilla-labs-jet...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mozilla-labs-jetpack?hl=en.
>
>
nsJetpackAudio kills the browser during startup.
Christian
Worked with the mercury code before the 0.8rc1 tag
On 29 Jan., 23:53, Jeff Balogh <m...@jeffbalogh.org> wrote:
> wfm on 3.7 on OS X. Hooray!
>
When will this be "compatible" with Firefox 3.7a1pre? Something like
10,000+ people testing out Firefox 3.7a1pre. :)
Can you be more specific? Do you get a crash report? How are you sure
it's the Jetpack Audio? Do you have any jetpacks installed that use
the audio component?
Did it work with the revision immediately prior to the 0.8rc1 tag?
There we no code changes for that revision, so I don't really see that
being possible.
I have tried using a fresh installation without any jetpacks and no
other add-ons as well as a normal system. The behaviour is always the
same.
As soon jetpack is activated the browser process fails to pass the
initalization. This means before the browser window is opened, the
process stops/dies. Only with jetpack completely deactivated the
browser will work "normally".
I assume that it is related to nsJetpackAudio because the last message
before the process ends is from jetpack referring to nsJetpackAudio.
I try to provide a log trace later.
C.