Re: 0.9.7 branch and bug 114377

2001-12-17 Thread dman84
dman84 wrote: dman84 wrote: dman84 wrote: I'm curious how many talkback reports were generated from this myself, but it appears to potentially affect anybody running Windows. That's probably a sizable number. If there's more to it than just the O/S, like a particular graphics card

Re: 0.9.7 branch and bug 114377

2001-12-17 Thread barney
dman84 wrote: this thread has several links for developers to find the crash data listed.. have a look. This is the only link you need: ftp://ftp.mozilla.org/pub/data/crash-data/ What I find interesting is that the #1 top crasher for the past week is a bug that was fixed 10 days ago.

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Sören Kuklau
JTK [EMAIL PROTECTED] schrieb im Newsbeitrag news:[EMAIL PROTECTED]... Sören Kuklau wrote: I wonder why you're still posting in here if you don't want to use Mozilla anyways. On the absolute contrary my Deutchlander friend, Oh you guessed right, I'm from Germany. Now what? I

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread DeMoN LaG
Jonas Jørgensen [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 16 Dec 2001: Sören Kuklau wrote: Oh look, I just right-clicked in 4.7x's email composer. Guess what I saw - yep, a CONTEXT MENU! Undo, copy, cut, paste... they're all there! Well... there's the

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread cmorley
barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. It's hard to imagine anyone using a release

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Jonas Jørgensen
DeMoN LaG wrote: Context menu for HTML message compose window (bug 98608) is targeted at Mozilla 1.0. It has the nsbeta1+ keyword, meaning that it has been accepted as a must-fix for the next Netscape release. Oh my god, you mean, *gasp*, that if they are marked nsbeta1+ that, and let me try

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Ian Thomas
Jonas Jørgensen wrote: Someone has been reading too many Mike Angelo articles. Don't you mean someone has been reading Mike Angelo's article too many times? Ian

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Ian Thomas
Ian Thomas wrote: topcrash is totally relative - you will always have topcrashers. If you have a single crasher, then that is a topcrasher. barney wrote: I'm not sure I follow you on this, at least in this case. Somebody even commented in the bug This is a topcrasher with recent MozillaTrunk

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Sören Kuklau
Ian Thomas [EMAIL PROTECTED] schrieb im Newsbeitrag [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Sören Kuklau wrote: Btw, this news message was written on Microsoft Outlook Express 6.0 on a Microsoft Windows XP Professional system. And not with MozillaNews. Why not? Because in my opinion,

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Holger Metzger
Am 16.12.2001 19:20 schrieb Sören Kuklau: I know that they're improving a lot, and I tried it, but it's still not enough for me to switch. I think I will at Mozilla 1.0. Outlook Express has so many bugs, especially in the editor... even Mozillas old Mailstones were superior in that area.

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Sören Kuklau
Holger Metzger [EMAIL PROTECTED] schrieb im Newsbeitrag [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Am 16.12.2001 19:20 schrieb Sören Kuklau: I know that they're improving a lot, and I tried it, but it's still not enough for me to switch. I think I will at Mozilla 1.0. Outlook Express has

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread Jonas Jørgensen
Ian Thomas wrote: Someone has been reading too many Mike Angelo articles. Don't you mean someone has been reading Mike Angelo's article too many times? Whatever. Someone has been reading too many of Mike Angelo's articles too many times :-) -- /Jonas

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread dman84
DeMoN LaG wrote: JTK [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 15 Dec 2001: Did you ever try Netscape 6.0? That abomination was more bug than burger, and they let it out the door. If you're asking AOL And Company how serious a bug has to be to block release,

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread dman84
I'm curious how many talkback reports were generated from this myself, but it appears to potentially affect anybody running Windows. That's probably a sizable number. If there's more to it than just the O/S, like a particular graphics card or something, there's no info on it. 2) How

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread dman84
dman84 wrote: I'm curious how many talkback reports were generated from this myself, but it appears to potentially affect anybody running Windows. That's probably a sizable number. If there's more to it than just the O/S, like a particular graphics card or something, there's no info on

Re: 0.9.7 branch and bug 114377

2001-12-16 Thread dman84
dman84 wrote: dman84 wrote: I'm curious how many talkback reports were generated from this myself, but it appears to potentially affect anybody running Windows. That's probably a sizable number. If there's more to it than just the O/S, like a particular graphics card or something,

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread Malodushnikh
AOL and Netscape would be perfectly happy releasing a bitmap image and calling it a browser. In article [EMAIL PROTECTED], JTK [EMAIL PROTECTED] wrote: barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed?

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread Raoul Truontine
bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. It's hard to imagine anyone using a release where you can't right-click on images or you'll crash.

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread Sören Kuklau
I wonder why you're still posting in here if you don't want to use Mozilla anyways. Your comments are uncalled for, not helping, and just plainly annoying. To put it shortly, shut up. (and btw, i know more and more people _using_ Mozilla _on_Win32_, so there _are_ quite many out there) JTK

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread Ian Thomas
barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. It's hard to imagine anyone using a

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread barney
Christopher Jahn wrote: Windows 98SE, Mozilla 0.9.6, build 2001112009 I can't make it crash by right-clicking any of the images on the pages referenced by Bugzilla - I simply get the expected context menu. Perhaps it's a flaw in the nightlies? Absolutely. You're on an old build, so of

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread barney
Ian Thomas wrote: barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 That argument about it being a topcrasher doesn't really carry any weight. topcrash is totally relative - you will always

Re: 0.9.7 branch and bug 114377

2001-12-15 Thread RV
barney wrote: barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 Branching doesn't mean they are releasing the 0.97. It means developers are allowed to keep working on the trunk, adding fixes, features

0.9.7 branch and bug 114377

2001-12-14 Thread barney
I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. It's hard to imagine anyone using a release where you

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread Christopher Jahn
And it came to pass that barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. It's hard

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread barney
Christopher Jahn wrote: And it came to pass that barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread Christopher Jahn
And it came to pass that barney wrote: Christopher Jahn wrote: And it came to pass that barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread DeMoN LaG
Christopher Jahn [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 14 Dec 2001: Until this message pointing to it, I was unaware of the bug. I use this function a lot with no problems. If it's as endemic as you say, I would have expected to have heard a lot more

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread JTK
barney wrote: I'm curious why mozilla is branching with a top crasher bug not yet fixed? http://bugzilla.mozilla.org/show_bug.cgi?id=114377 IMO, leaving this bug in 0.9.7 will make it pretty unusable, definitely degraded, for a lot of Windows users. Yeah, but how many of them are out

Re: 0.9.7 branch and bug 114377

2001-12-14 Thread DeMoN LaG
JTK [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 15 Dec 2001: Did you ever try Netscape 6.0? That abomination was more bug than burger, and they let it out the door. If you're asking AOL And Company how serious a bug has to be to block release, you couldn't be