M10 Out! You Thought They Skipped It?
Friday October 8th, 1999
Well, the plan was that they were going to skip an M10 build and go straight to M11. However, they decided that to reach beta they needed a bit more time (which is why beta is now scheduled for around 12/15/99), so they're spinning an M10 build to help with regression checking.
Be sure to check out the first Milestone appearance of the DOM Viewer (Debug>DOM Viewer) which allows you to see the DOM tree for a page. Also, if you haven't checked out Mozilla since M9, go back through our archives and you'll find news on new functionality that you can try for yourself.
BTW, proxies do work. Check out the comments at the bottom of this bug page to see how...
Also, we'd love to see some reader assessments of M10. Submit them in our Reader Reviews and we'll post them. Your review can be as long or short as you desire, but if it's around 500 words, you're 1/5th of the way towards a stuffed Mozilla. You don't have to use the entire 500 words on just M10 - you can give us your feelings about how far Mozilla has come, what you hope to see at beta, at release, etc. The Reviews section is for you all to have a place for your opinions, whenever you feel the urge to say something. It'll always be there if you feel the need to rant or rave...
UPDATE: If you are having trouble getting M10 to start in Windows, try deleting the mozregistry.dat file in your C:\windows directory.
We have two reviews of M10 for you to check out. Click the links in the box at the top of the page, or get to them visiting the Reader Reviews area (there's a link in the navbar at left).
#43 To fix Fonts in Linux: see release notes
Sunday October 10th, 1999 7:34 AM
You are replying to this message
The M10 <A HREF=<http://www.mozilla.org/pr…ey/release-notes/m10.html>> release notes</A> state that "If the fonts are too small in your environment, it may be possible to alleviate this by setting a preference in Mozilla. Add a line like the following to the preferences file (~/.mozilla/prefs.js): user_pref("browser.screen_resolution", 120);
This sets the dpi to 120. If you set the pref to zero (0), Mozilla will use the X server's dpi value. If the pref is not set, it uses the default value of 96.
If your fonts are still too small (or too large) after setting the DPI correctly, you can adjust the font size as follows:
setenv GECKO_FONT_SIZE_FACTOR 1.5
Note that the latter only affects fonts. The screen_resolution preference affects anything that specifies absolute size (e.g. CSS "pt" points).