Mozilla 1.0 RC1 Released

Thursday April 18th, 2002 today released the first 1.0 Candidate, in preparation for a final 1.0 build. They'll be using RC1 to evaluate where the 1.0 branch stands as far as crash bugs, and other things that are tracking. RC1's changes since 0.9.9 include the abilty to view the source of a cgi (the most duped bug), reorganized context and main menus, LDAP over SSL, return recipts, new animated mail alerts on Windows, Download Manager, final xul syntax changes, and numerious other bug fixes.

You can download RC1 from's Releases Page or read the Release Notes. We highly encourage you to download the talkback enabled builds, so crashes can be found and logged prior to 1.0. (These pages haven't reached yet, you can grab builds from the FTP site.)

Once people start using RC1 and get a handle on how the reception of it goes, they will be deciding whether or not to release another candidate or 1.0 itself. We'll keep you updated on this process, and let you know what is decided.

#191 I would like to see a Composer Forum

by PaulB <>

Tuesday April 23rd, 2002 6:56 PM

You are replying to this message


"Thanks for bringing up these issues -- they're important, and they do merit serious thought and discussion. Maybe we should start a Composer topic in the Forums?"

I would like to see a composer forum--maybe such a forum could be set up here or in the newsgroups.

Let me clarify my reference to FrontPage:

1. I know that few persons doing serious web design are using FrontPage. Still it is used a lot by persons doing mid and low end work. The high end users use something better.

2. Composer and Frontpage are targeting a similar group of developers. Many develope non-comercial sites, but some commercial sites are presaently developed with Frontpage, although most of these comercial sites use Frontpage because of its low cost.

3. Often when a site fails to work in Mozilla, especially the non comercial or siyes developed by smaller companies Frontpage has been used to develope the site. If Composer was further developed and improved, maybe more people would choose it over IE.

I will give you one example why the improvement of Composer is so important. I live in Winnipeg, Manitoba. The only web site listing Movie times and links to trailer was developed by FrontPage. Guess what? Mozilla could not go beyond the first page and find out which movies were playing at which theater. I emailed the web designer and he said he would not change it since it worked im Internet Explorer. The fix was very simple and I am not a very accomplished web coder, but I drafted up a compatible page. Now it works. This would not have happened if Composer was able to do more and be more functional and had better acceptance among more users.

If we want sites such as this one to drive people away from W3C compatible browser to IE then abandon Composer. If we want people to be able to use W3C compatible browsers (i.e. Mozilla) then Composer must recieve continued developement and much needed attention. At the low end, cost wise, for web development there is only FrontPage. In this category Composer needs to be a strong player.