M10 Out! You Thought They Skipped It?Friday October 8th, 1999Well, 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. So, go get M10 for Win32, Mac, or Linux from the Mozilla FTP site. If you mirror it, let us know so we can post your mirror here. In the meantime, you can read the M10 release notes. 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). I just got M9 3 hours ago...now another (luckily) 5 meg download... As much as people (reporters) like to complain about delays/setbacks, I'm happy to see the Mozilla team taking the time to get it right. I hate nothing more than when I'm using IE and it brings down the task bar. Unfortunatly, the quality of the product doesn't ensure public acceptance. :-( I know the BeOS build was brought to M8, but I haven't seen any builds after that. Why aren't they doing nightly builds on Be, and why isn't there an M10 release for BeOS? BeOS is not a "primary platform" for mozilla.org at this time. The M8 builds were released by the BeZilla team, which includes a person from Be Inc. You'll have to contact them. Try asking on the moz.beos newsgroup. shouldn't the nightly m11 builds be better than this release? As I understand it the M builds must contain all the features listed, but my also contain additional feature. They will be more stanble than the nightly releases, generally. Lemming Haven't tried M10 - but I downloaded an M11 nightly just before finding this out and it seems to run OK - not sure if I'll be able to post this tho... I downloaded M10 for Linux but it fails loading the library libstdc++-libc6.1-1.so.2. Where can I get this version of the library? I have libstdc++.so.2.7.2.8 and libstd++.so.2.8. I have the same problem. I'm running SuSE 6.1 and have installed glibc 2.1 My guess is that the binary package is compiled against some distribution specific .so files. Rather irritating, because I can't get the thing to compile either. This stupid Mozilla team is really made from a bunch of lazy people. I have never seem so many "Nothing much in this week's report" in a weekly summary in any other project. Hey, they are full time programmers and they also have 'nothing to show you for this week' kind of weekly achivement. Mozilla will fail not because it is open sourced but because they hired a bunch of lazy coders. I'd rather wait for Opera and paid for a browser but again, opera missed their deadline too at the mean time. They may be lazy in your opinion, but at least they have some pride in releasing something that is stable and as bug free as possible, unlike IE. If you can't wait for Mozilla, then stop complaining and go off and use your Opera. I'd rather have something that doesn't crash and take down the OS, and something that is free on top of that, and wait just a few more weeks. there's little more humiliating than to see no replies whatsoever to your post. Save your arguments for intelligent posters. You really don't know what you're talking about, and we don't take kindly to baseless insulting in our forums. Please refrain from doing so in the future. Ok Mr. Buttmunch, what exactly have YOU contributed to of late? Can you name anything that YOU'VE done other than sit and jockey your mouse? Do us all a favour and turn your computer off. Go take a walk and find another hobby. It's really EASY, isn't it Mr Lazy Ass, to sit back and criticise the work of volounteers while you contribute absolutely ZILCH. Yeah I know this idiot is probably a troller...or probably not. Every free software project out there gets hecklers like this. I have no doubt that there are really lazy ass morons like this out there who have breezed in from the Windows world where it's "just fine" to criticize everything, because it's always been given to you on a silver Microsoft platter. Yeah...damn lazy...just like those United Way, Red Cross, Salvation Army, and Peace Corps people....darn lazy pigs...working for nuthin and giving it all away...the nerve Do not confuse lots of people too busy to send out mozillazine status with lots of people being lazy. One can always see exact details of changes checked in to the mozilla repository using Bonsai cvs query form... http://cvs-mirror.mozilla.org/webtools/bonsai/cvsqueryform.cgi?cvsroot=/cvsroot&module=SeaMonkeyAll The two clicks will produce the following query showing the changes made in the last week... http://cvs-mirror.mozilla.org/webtools/bonsai/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=week&mindate=&maxdate=&cvsroot=%2Fcvsroot Checkins of tens of thousands of lines of changed code from over seventy people in one week is hardly laziness! This build doesn't even run here. XPCOM.DLL crashes every time...<argggh!> I had the same problem, but I installed the M10 build over a M9 (in the same directory). I did take the precaution of deleting the C:\Windows\Mozregistry.dat file, but obviously some other files were left in the binary directories. I solve this problem by deleting all the previous installation files and it worked ! Try to delete the mozregistry.dat file in your windows-directory. That should help. I'm sad. Very sad. Seems that there will (again) no Solaris SPARC version... Well get lxrun and use the linux binary. Aaaggggrrrr. Read the message before writing replys. I was talking about Solaris SPARC. SPARC SPARC and not dumb x86 !! OK, M10's out - and working/looking good, as far as I could see after a few minutes of testing. But when beta is scheduled later now, when do they plan to bring out the final release? I think almost the whole world except Microsoft is waiting for netscape 5. So they should try to do best quality but not forget time! Downloaded it quickly (ADSL: nice!) and ran it on my Linux laptop. It's zippier than what I remember, but it really needed the ~/.mozilla directory to be nuked -- wouldn't start otherwise. And yes, my XML/CSS pages still render; great! What's annoying, I see lots of display turds. They overwrite the "file" menu with button images, leave part of the horiz scrollbar for those leftmost panes when I hide them. When I viewed www.ora.com I got LOTS of horizontal lines drawn across the screen. In summary -- the "Debug" and "QA" menus are clearly there for a good reason! But progress is visible. - Jojo see http://www.bucksch.org/mozilla/thelostmilestone.html Ben Bucksch (waiting for his validation mail) Which binary do you run to get interface? Im currently running the viewer.exe binary. Thanks Sam Where are the fullcircle enabled builds? I like the fact that whenever Mozilla milestones crash a fullcircle build will submit the crash data back to them,
M10 is running great. Loads pages way faster than Netscape, and looks nice witht eh slick blue interface. But 2 bugs are, well, bugging me. The first one is, if you click on the Mozilla or Open Windows button on the bottom taskbar, Mozilla crashes. The other one is, Mozilla isn't saving the browser window size when Mozilla closes. But besides these 2, it's running fine. :) Can someone tell me what this shared library is part off. I'm trying to run it on my RH 6.0 box. I have the same prob with Mandrake 6. run-mozilla.sh works though although the interface is a bit clunky. i had problems with that lib too. upgrading glibc from 2.0.6 to 2.1.2 helped. (glibc 2.0 is not thread safe!) Linux users; dont forget to remove the mozilla directory in your home directory if you have a previous mozilla install. I could not get M10 to run until i removed the mozilla directory in my /usr/local and removed the mozilla directory in my home directory, and installed M10 fresh. Windows; I had no previous install, but there is a similar something you must remove. The browser works decently well, much better than past milestones. It is useable. Be aware to focus your problems, fustrations, and bug-reporting to bugzilla. Linux users; dont forget to remove the mozilla directory in your home directory if you have a previous mozilla install. I could not get M10 to run until i removed the mozilla directory in my /usr/local and removed the mozilla directory in my home directory, and installed M10 fresh. Windows; I had no previous install, but there is a similar something you must remove. The browser works decently well, much better than past milestones. It is useable. Be aware to focus your problems, fustrations, and bug-reporting to bugzilla. I have to say that I've enjoyed watching mozilla grow from the project that could...to M10. M10 is feels much more mature than the other releases. Its fast, its small, its every web developers dream, damn this thing rocks. So this message is going out to everybody who has helped track bugs, write code, test software: you guys rock! Keep up the good work. Writing in the M10 Mac build. This is by far the best build to date and it looks like things are improving quickly. Rendering is wonderful and fast. Startup seems great, 5s on my G3-350, compared to 3s with 4.7; I'm sure it will be faster than Nav by release time. Interface 'feels' more responsive. Contextual Menus are really nice to see. No crashes!. Feeling more and more like a daily browser and we're not even close to beta. Now if only the majority of the preferences and shortcuts would work. Also, JS seems slow (like IE). Keep up the great work! I'll have to try a M10 on N/T to see how far things have *really* progressed. Yo! The DOM Viewer is awesome, even if I can't figure out how to shut it down again without closing the browser. On my Win95 box, M10 DID remember to open fullsize upon shutdown/reboot. The save password thingy crashed it, tho. But it's fast and context menus are coming along VERY nicely. Another tip of the hat to all the coders! compared to a syntax colored outline view with full attributes listing. Common, IE5 blows this feature away. You can't even see the attributes! I don't see the hype. talk is cheap design a better system, or shut up. IE5's view is structural just like M10's. It displays things in a tree-format just like the DOM Viewer. The difference? It displays each tree row in a nice syntax-colored mode with attributes displayed, and frankly,looks far better and more useful than M10's. Also, IE5 has a context-sensitive "web helper" that allows an identifcal to M10 DOM Viewer too. I don't see why I have to invent a better one to simple observe that IE5 has both Mozilla's DOM style available, and a far superior combined syntax-colored-source-view +structural view. there we go, your points are noted. you don't have to invent a better one, merely give a spec'n of what you'd like to see added. I'm sure that also counts as "design". See, if you'd posted this in the first place, without words like "sucks", etc, which berate the hard work of individuals, we could have taken this as suggestions for improvement from the word go. Thank you for your time. This is about a fine-grained structural view. What you want sounds like the ability to collapse in view source, which is entirely different. Well I've downloaded a nightly build every once in a while, but one thing has really got me nuts: Go check http://www.kolumbus.fi/seppo.j.aaltonen/shatter/ The page doesn't render correctly in 4.7 or M10, but in ie, yes. So, if you nice'n'beatiful people would tell me what's wrong? (I don't use ie, but the maker of the site does). Looks like they didn't make their Javascript compatible across browsers. The problem is this: No browser out there correctly supports the DOM -- Document Object Model -- yet (Mozilla is mighty close, though), and IE and Communicator both had their own proprietary object model. It would be very easy for the site's webmaster to write some Javascript code that would be cross-browser compatible, but he has decided against that. Eventually, when all browsers move to using DOM the way the W3C recommends, he'll only have to write code to that recommendation, and it will work on browsers that support it. Aloha, I am testing the Linux build in a resolution of 1600x1200 and have the problem that fonts are so small that they are unreadable. That also applies to widget fonts, menu's, etc. I know there is a way to change this, but foolish /me forgot how. Can anybody help? Thanks in advance. The M10 <A HREF=http://www.mozilla.org/projects/seamonkey/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. There is some info about setting the X server's DPI value at <A HREF=http://www.mozilla.org/unix/dpi.html>http://www.mozilla.org/unix/dpi.html</a>. 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). The M10 release notes (http://www.mozilla.org/projects/seamonkey/release-notes/m10.html ) 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. There is some info about setting the X server's DPI value at (http://www.mozilla.org/unix/dpi.html). 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). Aloha, I am testing the Linux build in a resolution of 1600x1200 and have the problem that fonts are so small that they are unreadable. That also applies to widget fonts, menu's, etc. I know there is a way to change this, but foolish /me forgot how. Can anybody help? Thanks in advance. I'm not sure how M10 could possibly qualify as a "milestone" build if it doesn't run on Win32. After downloading and extracting M10, and then running apprunner.exe, I get this error immediately: APPRUNNER caused an invalid page fault in module XPCOM.DLL at 0167:60ad1510. Registers: EAX=00000000 CS=0167 EIP=60ad1510 EFLGS=00010216 EBX=010ad010 SS=016f ESP=0063eeb8 EBP=0063efc0 ECX=000000a1 DS=016f ESI=0063eff0 FS=477f EDX=81716f8c ES=016f EDI=0063efec GS=0000 Bytes at CS:EIP: 80 38 00 74 08 50 8b ce e8 1e fa ff ff 5e c9 c3 Stack dump: 0063eff0 00000100 0000010c bff7b9c5 816f59bc 0000010c 780012b1 00000020 00000100 0000010c bff7b9c5 0000003f 0063ef84 016ec3a0 bff7b9c5 816f59bc Kris OK, here we go again: Delete the mozregistry.dat file in your windows-directory. Then it should work fine. OK, so it's still to be considered a Thrill-seekers release at this point, but having to delete obscure files in the system directory in order to make it work is not high on my list of positive recommendations. Well, all it means is that you installed a previous build at some point. If you're gonna play the check-out-the-latest-build game, you gotta play by the rules: don't expect things to behave like an actual release. I just d'l'ed the thing, and it won't save the proxy information. I must say, I am starting get quite disappointed in Mozilla... Proxies have not hooked up to the user interface yet. Read the following link for how to set them up: http://bugzilla.mozilla.org/show_bug.cgi?id=8559 This is pre-release software. You should NOT expect everything to be working yet!! Are they aloud to just call this Netscape Communicator 6.0?? I am downloading it now and can't wait. This is great. The presentation of images have been improved. Now Mozilla renders images without spaces betwen them, and two of my sites now are rendered properly and fastly. But http://www.eurielec.etsit.upm.es/ renders awfully. Somebody knows if its a problem of the HTML code of this page, or I have to commit a bug report??? You see the same problems on other platforms??? [ I'm on Win32 :( ] The problem is that Mozilla breaks between images which are in table cells. It's reported in bug #4427 Geez, this is like kindergarten-level JavaScript -- and it's been done wrong. The author of this page used an IE-specific shortcut in his scripting. If he'd just done it correctly (by prefixing the calls to the image object properties with "document." like you're supposed to), there'd be no problem in *any* JS-compliant browser, including IE and Opera as well as Netscape or Mozilla. Moral: Don't place your sole trust in the documentation at MSDN. And take an extra 30 seconds to *test* your pages in multiple browsers before posting them. I've been following the releases of all the Milestones and most of time I download the nightly builds. Thanks to the person that recommended deleteing the mozregistry.dat thing in the windows directory. I was wondering why the darn thing kept crashing. Can't believe it this release even loads my website. WOoohooo!! Can't remember my password this post so I am anonymous BradyB - MozZineMember Where exactly is this DOM viewer in IE5? Or is it that thing you get when you load an XML file Hi, Just tried the M10 build & I've gotta say I like it a lot ! The search feature looks really promising... I wonder when Mozilla will get an installation routine (i.e. be installed like a regular app) Does anyone know ? Thanks, Rick Hi, Just tried the M10 build & I've gotta say I like it a lot ! The search feature looks really promising... I wonder when Mozilla will get an installation routine (i.e. be installed like a regular app) Does anyone know ? Thanks, Rick I don't think they'll add an installer until it hits beta since there's no real need for it right now since not everything is suppose to be consumer friendly while it's still in development. I mean if it were to be completely consumer friendly right now the DOS window would not show when you run Mozilla since that will confuse a lot of people. But if I remember correctly they is work being done in an installer app. The Win version is far buggier than M9 - the new controls like this edit box don't work (try entering more than two lines and it fails to wrap; try backspacing and watch graphics; etc.) - and it renders mozillaZine wrong (first paragraph in the topic description at top of this page is in correct font, remaining paras are in Times.) That said, right-click menus now work, which is a "hallelujah" occasion as far as I'm concerned :) (One step forward, two steps back? :) --sam (going to see if all those bugs are known) Just to note that I tried the current nightly build and the edit box works a lot better (it still wordwraps incorrectly but only slightly, I reported that as a bug [I'm somewhat hesitant about reporting bugs since the query system is so incomprehensible, but i don't tHINK it was there already]). Form elements are really badly screwed in M10/Win in general though; trying to use it for bugzilla was a joke. :) In nightly build they are at least usable. I'm glad there are several months until a beta is supposed to be done because they're going to need every minute of it :) --sam Remember, in general 'tis better to report the bug and have it be a duplicate than to not report it. Sometimes, the duplicates are hard to find using search terms (for instance, when I reported an incorrect rendering of the Box Acid test, there was a dup of it in terms that I would have never thought to search for), but it's still better to report a non-obvious dup than to not report. :) At the top of this page it says that the beta release will be 12/15/99, but at mozilla.org, seamonkey milestone page, it says that m13 will wind down to a beta release on 2/15/00. Which is it? The latest build has a pretty spiffy "New Profile" dialog...I hope it's a prediction of things to come. I'm still waiting for preferences to save before I can really use Mozilla for anything other than testing. Looking better than ever - but despite hand editing the prefs.js file according to the bugzilla link (and triple checking it!), http proxies still don't work for me. All I see is the rotating barber pole graphic, a context-proxy-menu message, and that's all. panelvan how to cope with this: /opt/pgcc/bin/gcc -o regExport regExport.o -Wall -Wshadow -Wpointer-arith -Wcast-align -pedantic -Wno-long-long -O6 -march=pentium -pthread -L../../../dist/bin -L../../../dist/lib -lxpcom -lmozjs -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXext -lX11 -lm -lplds3 -lplc3 -lnspr3 -lpthread -lintl -lnsl -lutil -lresolv -ldl -lm -lstdc++ ../../../dist/bin/libxpcom.so: undefined reference to `PL_IsQueueOnCurrentThread' I'm still running a nightly build from early in the month... none since then run, not even M10! What's up here? The M10 build for Solaris SPARC is ready and out. URL is http://puck.informatik.med.uni-giessen.de/download/mozilla-sparc-sun-solaris2.7-M10.tar.gz ftp.mozilla.org will follow. I see that many people here have problems with installing M10... If I were you, I would read Release Notes (you can find them atleast from http://www.mozilla.org/projects/seamonkey/release-notes/m10.html). It has got instructions how to install M10, and how to remove previous builds. It will save much time... |