Mozilla 1.1 Beta Out And About

asa writes: "Today mozilla.org released Mozilla 1.1 Beta. New to this release are full-screen mode for Linux, BiDi Hebrew improvements, Arabic shaping improvements for Linux, and significant improvements to Venkman, the best cross-platform JavaScript debugger on the planet. Binaries and release notes available at http://www.mozilla.org/releases/. You can read more about this release at mozilla.org and mozillazine.org and if you want to see how this release fits into the overall 1.1 development cycle there's a pretty picture available at the Mozilla Development Roadmap."

Comments

Bug in favorite feature

[palme999]

"Use of Mozilla's "quicklaunch" (AKA "turbo") mode may cause the deletion of user preferences. It is recommended that you do not run quicklaunch until this bug is fixed."

Checking bugilla shows a patch in the queue, here's hoping it makes it to one of the nightly's.

Great on OS X

[d3xt3r]

Posting now using Moz 1.1 Beta on OS X. There are significant speed improvements to the interface and the Aqua fonts look great.

Mozilla has become so much better than IE lately that there is never a need to switch back and forth. Thanks Mozilla team, keep up the great work!

Tips for searching Bugzilla

[jesser]

Mozilla.org gets a lot of duplicate bug reports: 40-50% of a sample of bugs from April 2002 are dups. If you know how to search Bugzilla, you can get that down to 15-20%. (Knowing some jargon helps too, of course.) Unfortunately, the most widely advertised Bugzilla search tool, the query builder, is so complicated that many testers give up before finding their bug and report a duplicate.

There's a well-hidden search box on the Bugzilla front page that works a lot like Google. You can almost use it like Google, but there are several differences you should be aware of:

• Each word is matched as a substring of the summary (and several other fields). A search for 'auto compl' will match "auto-complete", "auto complete", and "autocompletion".
• Like in Google, you can use | to create disjunctions. For example, a search for 'address|location|url bar|field focus' will match "focus does not move when clicking outside of location bar". While "or" is usually unnecessary for general web searches, it is indispensible when searching for a specific bug report.
• By default, Bugzilla only searches for open bugs. If you're looking for a bug that has been reported several times, it may help to include duplicates in the search. One way to do this is to prefix the search with 'ALL ' in all caps. For example, 'ALL rename exe' will lead you to an often-reported bug (120327) that I should be helping bz to fix instead of posting this comment, while 'rename exe' will not find anything.
• If you know that the bug you're searching for is visible and popular, try adding 'votes:2' to your search. For example, 'ALL votes:2 context menu back' will find the newest flamewar-bug about the back command in the context menu among the 42 bugs that match 'ALL context menu back'. Searches that use votes:2 are several times faster than searches that include all bugs because bugzilla can start the search with an integer comparison.
• The search includes several fields, not just the bug summary (title). For example, in a search for 'mail compos focus', the word "mail" can appear in either the product name (MailNews) or the bug summary, and "compos" can appear either in a component name (Composition) or in the summary (compose, composing, etc). To restrict a search term to the summary, use '+term'.

Other useful tools for avoiding reporting duplicates include the frequently reported bugs list and #mozillazine on irc.mozilla.org. If you find yourself working in Bugzilla a lot, you can use the collect buglinks bookmarklet to get a list of bugs mentioned in a given bug report, which is useful because many bug reports include links to related bugs.

MOD PARENT DOWN

[RedSynapse]

The parent comment is *NOT* the release notes from 1.1Beta which this story is about. This is the release notes for 1.1ALPHA which was released over a month ago. The release notes for 1.1BETA are as follows.

• Improvements to Arabic shaping which result in better layout of Arabic pages on Linux and other platforms without their own Arabic support.
• A bug was fixed which caused English text in text boxes to be displayed in the wrong direction on Hebrew pages.
• The JavaScript Debugger has gone through a major development cycle. It now sports a palette of nine views which can be rearranged within the main window, or docked in separate floating windows. It is also possible to create user defined views and commands directly with JavaScript. More details are available in the FAQ, newsgroup, or IRC channel.
• Distinct window icons on MS Windows for the different Mozilla applications
• Mozilla on Linux now has Fullscreen mode. (press F11)
• All Search entry points now your default search engine.
• Improved site compatability and rendering.
• The tab bar now has a button for creating new tabs.

Antialiased Fonts for X

[krmt]

I don't know what you're going on about. I run Mozilla in KDE, and I've had antialiasing for months now, well before 1.0 hit. Debian includes it as a standard install option, and it can easily be turned on and off, and it will run with any X environment, including Gnome and Windowmaker.

Basically, if you don't have antialiasing, it's either your own fault or that of your distro.