Peter Potamus the Purple Hippo wrote:
> Daniel wrote:
>> Peter Potamus the Purple Hippo wrote:
>>> Phillip Pi wrote:
>>>> On 7/6/2007 8:52 AM PT, Wayne Mery wrote:
>>>>
>>>>>>>> FYI from one of the crashes if it helps.
>>>>>>> please post talkback id,
>>>>>>> http://kb.mozillazine.org/Mozilla_Su...AQs_:_Talkback
>>>>>> Stable SeaMonkey don't come with TalkBack.
>>>>> true - I am referring to trunk.
>>>>> Which IMO is the only build worth testing for this problem.
>>>> Are those trunks stable enough these days? I don't want to be using
>>>> a super buggy product. I do have to use it for hours and days to
>>>> reproduce it. Basically, is it safe to use on my production system
>>>> and use with the current extensions I have?
>>> hey, the current release of SM can be a "super buggy product."
>>>
>>
>> Peter, are you implying that SM is a super product that can be buggy,
>> or are you implying that SM is an extremely buggy product??
>>
>> In either case, I don't think the SM Council would be impressed!
>>
>> Daniel
>
> the best of products can be buggy whether its the final version or
> whatever.
>

But, in that case, it's usually just because the bug had not been found
yet! Just look at the various Windows bugs that only get found in the
wide world.

Daniel

Phillip Pi wrote:
> On 7/4/2007 7:33 PM PT, Wayne Mery wrote:
>
>> On 7/4/2007 5:27 PM, Ant wrote:
>>> FYI from one of the crashes if it helps.
>>
>> please post talkback id,
>> http://kb.mozillazine.org/Mozilla_Su...AQs_:_Talkback
>
> Stable SeaMonkey don't come with TalkBack. See
> http://groups.google.com/group/mozil...%26rnum%3D7%26
> or http://tinyurl.com/yt5veq ...

Talkback never worked right on Mac Platform actually causes crashes.

--
------------------------------------------------------------------------
Phillip M. Jones, CET http://www.vpea.org
If it's "fixed", don't "break it"! mailtojones@kimbanet.com
http://www.kimbanet.com/~pjones/default.htm
Mac G4-500, OSX.3.9 Mac 17" PowerBook G4-1.67 Gb, OSX.4.10
------------------------------------------------------------------------

Daniel wrote:
> Peter Potamus the Purple Hippo wrote:
>> Phillip Pi wrote:
>>> On 7/6/2007 8:52 AM PT, Wayne Mery wrote:
>>>
>>>>>>> FYI from one of the crashes if it helps.
>>>>>> please post talkback id,
>>>>>> http://kb.mozillazine.org/Mozilla_Su...AQs_:_Talkback
>>>>> Stable SeaMonkey don't come with TalkBack.
>>>> true - I am referring to trunk.
>>>> Which IMO is the only build worth testing for this problem.
>>>
>>> Are those trunks stable enough these days? I don't want to be using a
>>> super buggy product. I do have to use it for hours and days to
>>> reproduce it. Basically, is it safe to use on my production system
>>> and use with the current extensions I have?
>>
>> hey, the current release of SM can be a "super buggy product."
>>
>
> Peter, are you implying that SM is a super product that can be buggy, or
> are you implying that SM is an extremely buggy product??
>
> In either case, I don't think the SM Council would be impressed!
>
> Daniel

SeaMonkey has its warts. On the Mac side the Save As... command does
work as it should. using the short cut key Combo Option-S the first time
works the second time you hit it is supposed to save the file (or item).
It doesn't the window dismisses for split second and bounces back. and
nothing is saved.

I've posted a bug on it. The last comment on the bug was that yes it was
and was broken widget. After that point nothing has been fixed.
Something was said it might be fixed on the next major version release.

But despite this I still wouldn't use anything else including FF/TB
unless I have to.

--
------------------------------------------------------------------------
Phillip M. Jones, CET mailtojones@kimbanet.com
If it's "fixed", don't "break it"! http://www.vpea.org
http://www.kimbanet.com/~pjones/default.htm
------------------------------------------------------------------------

Daniel wrote:
> Peter Potamus the Purple Hippo wrote:
>> Daniel wrote:
>>> Peter Potamus the Purple Hippo wrote:
>>>> Phillip Pi wrote:
>>>>> On 7/6/2007 8:52 AM PT, Wayne Mery wrote:
>>>>>
>>>>>>>>> FYI from one of the crashes if it helps.
>>>>>>>> please post talkback id,
>>>>>>>> http://kb.mozillazine.org/Mozilla_Su...AQs_:_Talkback
>>>>>>> Stable SeaMonkey don't come with TalkBack.
>>>>>> true - I am referring to trunk.
>>>>>> Which IMO is the only build worth testing for this problem.
>>>>> Are those trunks stable enough these days? I don't want to be using
>>>>> a super buggy product. I do have to use it for hours and days to
>>>>> reproduce it. Basically, is it safe to use on my production system
>>>>> and use with the current extensions I have?
>>>> hey, the current release of SM can be a "super buggy product."
>>>>
>>>
>>> Peter, are you implying that SM is a super product that can be buggy,
>>> or are you implying that SM is an extremely buggy product??
>>>
>>> In either case, I don't think the SM Council would be impressed!
>>>
>>> Daniel
>>
>> the best of products can be buggy whether its the final version or
>> whatever.
>>
>
> But, in that case, it's usually just because the bug had not been found
> yet! Just look at the various Windows bugs that only get found in the
> wide world.
>
> Daniel
as as described in a previous post; either, a Lack of interest, or a
lack of personnel to fix.

--
------------------------------------------------------------------------
Phillip M. Jones, CET mailtojones@kimbanet.com
If it's "fixed", don't "break it"! http://www.vpea.org
http://www.kimbanet.com/~pjones/default.htm
------------------------------------------------------------------------

On 7/6/2007 4:11 PM, Phillip Pi wrote:
> On 7/6/2007 8:52 AM PT, Wayne Mery wrote:
>
>>>>> FYI from one of the crashes if it helps.
>>>>
>>>> please post talkback id,
>>>> http://kb.mozillazine.org/Mozilla_Su...AQs_:_Talkback
>>>
>>> Stable SeaMonkey don't come with TalkBack.
>>
>> true - I am referring to trunk.
>> Which IMO is the only build worth testing for this problem.
>
> Are those trunks stable enough these days? I don't want to be using a
> super buggy product. I do have to use it for hours and days to reproduce
> it. Basically, is it safe to use on my production system and use with
> the current extensions I have?

As a general rule I find trunk to be a stable operating environment, but
it does go through periods of minor to major instability - you just
stick with one that looks good.

However, in the present context I suppose it really comes down to what
you want more - a solution to the problem, or 100% safety with all your
extensions.