I tell you that I'd like to thank Mozilla developers which have done a great job fixing up Mozilla in the past week for the Branch freeze.. About a week ago, if you would of tried mozilla it was broken in many ways.. but build 1-22 (w2k as I can see), is by far one of the better builds to date... developers know who they are. Thanks guys.
the fact that Print-Preview crashes, argh, and its not outputing correctly when it doesn't crash, is one that is still a bad bug, but it should be fixed hopefully by 0.9.8 milestone is released. > These "harmless bugs" that can be easily fixed later should be fixed now! I agree, but unless there are more volunteers/developers, and more time to fix these sometimes without fixing the back-end for this code in the first place, it is useless to fix the front-end code that uses the back-end code, its more of a waste of developer resources otherwise. See there are several bugs that are deamed more important first: Like 71668, and mozilla 1.0 tracking bugs that hopefully will address alot of the rest of the API problems/freezes and performance. Most of the bugs now are stuff that are trying to address: are ones that come up after patchs land, and specs to getting the groundwork laid API wise, the functionality/UI specs should be doing what is suppose to with those API's being frozen for Mozilla 1.0, and as blake said distribution releases related bugs for feature landings. And stuff that they exposed that developers didn't know it was broken till they fixed the back-end code that came before the front-end code.. Sure there is alot of stuff that doesn't work ok.. There is not that much the average user cant do with Mozilla currently, and there are bugs here and there.. both visually obvious stuff, back-end related, functionality is not complete on features that are already in, networking code, page loading.. Xcross platform API stuff, and the general functionality that IE/Outlook provides all is really what 1.0 is about.. and there are a few bugs that are deamed needed fixing for a bad user experience. There is a handful more on just re-aranging menu options, and the look of dialog boxes, etc. >These type features are things that people hold very personal and they >want them working. Many bugs are for people who have real issues which hinder their ability to use Mozilla, or hinder their ability to code the rest of the features/functionality or fix front-end bugs, both in certain environmental situations & page content related... others are just general anoyance bugs that hopefully will get fixed when they are demmed necessary as a major usage blocker for most who would be using it, but as I see mozilla, for these average users, you can live without the bugs being fixed for now. Take for instance: Windows 2000 has 63,000 bugs.. that are open issues. Mozilla has way less than that, but you look at Windows 2000 and people say it works fine for the average user. (example counter argument, except gaming), most of the bugs are for Networking/Servers/Admins.. etc that are deamed really bad bugs for their general usage. Like MS puts winXP: is all about the out of box end-user experience, and usage modal of the users of the product, that is one reason Window 2000 took about 4 years before it came out. Its all about what is more important. Mozilla itself, is still a work in progress, but as every other work-in-progress, sometimes it gets worse before it gets better, this happened on the road from 0.9.7 to 0.9.8.. and many crashes have been fixed in the last week. Managing bookmarks works way better now then before, still slightly buggy.. but Its more use-able now than before, thanks to back-end code that was for other bugs. I've been following checkin's, bugs for awhile including mozilla progress (status pages) since milestone 0.6 released (hint Netscape 6.0 PR1).. and this is better than it has ever been to the average user, except the fact that print preview is crashing.. and plug-ins are not currently acting correctly in my personal experience on dialup.. :) >The commitment by talented individuals is there forsomething really >superior, but maybe some of these realizations aren't materializing in your brains. Right now, They're there, but it takes fixing mozilla's foundation first.. I've personally got ideas about projects that are beyond stuff that you've even seen MS talk about: I could start creating some specs (right now I have some sketches on paper) if I had the mozilla framework set in stone and knowledge to understanding mozilla's api's and languages: e.g. XML & XUL and that my friend is where the real stuff is at.. Mozilla's codebase is where that could happen before you see it elsewhere, but it wouldn't do me much good without mozilla building the foundation for that. I'd say I'd share this with you but then I'd have to shoot you :) So finishing the foundation on the building is more important that adding trim to the windows. You can't have one without the other first. -cheers.. dman84 psmith wrote: > You people are getting behind the curve... tabs are already totally > expected, for example. If you want to pick up some new people, your > tabs will need to save themselves at exit and you should make the tabs > schedule reloads (so the user gets updates when HE wants) for serious > users of a browser for research and that will be part of raising the > status of Mozilla (Netscape) to being a browser for more refined tastes. > And it appears the feature you have for checking if there's changes on a > page does not work. This isn't just a simple bug that can be fixed > sometime later. And neither is the History feature which loses its sort > order every time it is closed. These "harmless bugs" that can be easily > fixed later should be fixed now! You are not endearing too many people, > and you need to do just that so that these people who are right now > testing your software can really have something to tell other people in > the general population about! These type features are things that > people hold very personal and they want them working. These days, if > something's going to become popular in the marketplace, it already does > amazing things that satisfy people before it even is being widely sold > or made available. > Certain web pages that have dhtml are going to have to scroll faster, > now. Back and Forward are going to have to load pages already seen just > as fast as Internet Explorer. > And, in general, Mozilla programmers are really going to need to knock > themselves out to come up with that which other browsers will simply not > be able to do for a long time. The commitment by talented individuals > is there for something really superior, but maybe some of these > realizations aren't materializing in your brains. There is not a lot of > time to make this thing great and get it noticed. >
