Linked by Thom Holwerda on Tue 20th Nov 2007 16:54 UTC, submitted by lefty78312
Mozilla & Gecko clones The Mozilla Corporation today released Firefox 3 Beta 1, which is now available for download in a variety of languages. The beta includes updates to the default theme, the new places site management features, improved security architecture, and Gecko 1.9. Release notes with a more complete list of features, are also available.
Thread beginning with comment 285769
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Native widgets?
by djst on Wed 21st Nov 2007 10:37 UTC in reply to "RE[6]: Native widgets?"
Member since:

1) I have run Firefox 3.0b1 and subsequent builds - yes, bugs have been fixed, but memory usage is still far too high. Instead of fixing them, what I see in bugzilla is the constant blaming of Apple for all problems in the world.

Do you have any examples of where people blame Apple for all problems in the world?

Reply Parent Score: 6

RE[8]: Native widgets?
by kaiwai on Thu 22nd Nov 2007 05:16 in reply to "RE[7]: Native widgets?"
kaiwai Member since:

Read through there with the whining and whinging by developers over 'bugs'.

Interesting, they're never able to explain how millions of developers around the world don't suffer from the same issues as they do. I'm sure there are bugs in the framework provided by Apple but to blame them (look through bugzilla for more) for every bit of problems speak of incompetent programming than anything to do with Apple.

Reply Parent Score: 1

RE[9]: Native widgets?
by smitty on Thu 22nd Nov 2007 07:04 in reply to "RE[8]: Native widgets?"
smitty Member since:

I don't know whether the Mozilla developers regularly whine about Apple or not, but if they do that was a horrible example you gave us. Most of the bug was during Leopard's pre-release phase, so it's not a surprise that there might be a few bugs in there. What comments show up after?

This is marked as P1 because it is commonly reported, confusing, and
destabilizing. AppKit is getting into an essentially corrupted state.

Created an attachment (id=288560) [details]
test app v1.0

This test app demonstrates the OS bug. It does the same thing our app does, but
in a reduced way. Much easier to play with than our actual menu code.

Filed Apple bug 5598550 on the issue, which includes the test app.

Created an attachment (id=288616) [details]
fix v1.0

I found a way to handle menu bar swapping that doesn't trigger the AppKit bug.
This works on 10.4 and 10.5.

landed on trunk

That seems to me to be pretty much the perfect bug fix - there are no recriminations, no backstabbing, not even a hard time tracking down the bug. A quick simplified test case, followed by filing a bug in the upstream software, followed by a quick workaround. What exactly do you find so wrong about it? I'm sure there are similar bugs for working around issues that have been found with Windows and Linux as well.

Edited 2007-11-22 07:05

Reply Parent Score: 3