Slashdot Mirror

It does not. And probably will not till mozilla 1.0 or later... See the LDAP support tracking bug and the bugs that are blocking it for more details on the status of things.... I don't use LDAP, so I can't tell you exactly how far along we are based on the info in those bugs.

blech, anitmated gifs behaving isnt a story.

But stoping the popup bombs, let me be the first to say Thank you Jesus You can now stop popups, the one and only hack that I wanted to see come from open source mozilla and its finally in the tree. Kick Ass, read about it at Here

Well, then it's time to switch to Moz. Quoting the 0.8 release notes:

There are several new hidden prefs (UI will be added eventually) to turn off various annoying features on web pages:

// Use configurable security policies to override popups, see
// http://www.mozilla.org/projects/security/component s/configPolicy.html
// Turn window.open off for particular sites:

user_pref("capability.policy.popupsites.sites", "http://www.annoyingsite1.com http://www.popupsite2.com");
user_pref("capability.policy.popupsites.windowinte rnal.open","noAccess");

// Or turn it off everywhere:
user_pref("capability.policy.default.windowinterna l.open","noAccess");

// Override popping up new windows on target=anything
user_pref("browser.target_new_blocked", true);

Cheers,
-j.

That said, you are not the only one who wants this functionality. See http://bugzilla.mozilla.org/show_bug.cgi?id=11459. The discussion on that bug includes a way to fix it using Protozoilla. This fix is currently being considered for inclusion in the main source tree.

I would suggest watching http://www.mozillazine.org/build_comments/ and getting or not getting builds based on the excellent comments Asa puts up there.

I'm not sure why your text entry widget wasn't working; if you could file a bug report on it (http://bugzilla.mozilla.org) that would be great. The menu bug is a very recent regression and is being worked on.

Check out this bug report and series of discussions. What kind of development process is this? I've never seen something so chaotic with a product as complex as Mozilla. People are making minor changes breaking entire other parts of the program. Fundamental errors are going unseen for ages. Do they really expect to get a working browser out of this insane process?

I was happily chugging along on the daily builds until sometime around the first of the month. Apparently, they decided to stop asking what color preferences you want and instead use the colors associated with your gtk theme as the default colors for text/background for the displayed pages. Sites like appwatch are unreadable because they chose to use the secondary foreground color so I'm still using a build from about a month ago. The bug's been in bugzilla since Feb 2nd along with a patch and they still haven't bothered to check it in. I thought they were supposed to be in the process of fixing the bugs right now rather than adding "features". The other thing that sucks is I had to fire up Netscape 4.7 to post this because the text entry seems to break at every line so when you insert long URLs, it chops them up so they don't work. I'm still trying to find that one in bugzilla...

well, netscape 6.0 split off from the mozilla branch way back before M18 (http://www.mozilla.org/roadmap.html), so comparing Netscape 6 with a product released 3 versions later is a little unfair.

I sitll agree, netscape 6 sucks though.

P.S. This release was 2 days late! It was forcast for the 12th feb! (Well, arround).

Good job guys, keeping to a schedule. Should look forward to 0.9 about the 3rd week of march then, and hopefully 1.0 at the end of April.

Mozilla implemented then broke or removed

IE supports the hover: property for links. Mozilla is attempting to support it for everything. That's just a teensy weensy bit harder. We'll get there, though.

In addition, a Mozilla developer says "From reading the CSS WG mailing list, it looks like the exact definition of hierarchical hover is still being hammered out. I'm not sure we should put an implementation of it into our code until we are sure that we know how exactly this feature should work."

It's Bug 5693.

Gerv

You know, it's hard to transmit patches by voice from a car window.

Are you familiar with catdoc and xls2csv? I don't know how well they cope with text that is non-(8859-1) and non-unicode, though. As to the proprietory character set thing, the answer in the long run is unicode, but meanwhile mozilla 0.7 claims to have some Hebrew support.

On this system, all 64 Megs of RAM were consumed by Gnome and X

One of the fastest forms of interprocess communication under Linux is shared memory. However, top reports shared memory use incorrectly. For example, if two programs are loaded into RAM, and each is using 16 MB (8 MB for itself and 8 MB shared between the two), top will report 32 MB in use instead of 24. Under Linux, processes and threads are pretty much the same except that threads share memory; top barfs on multithreaded applications such as Mozilla. When X is running, top also reports your video card's RAM as in use by X and whatever apps are using MIT Shared Memory for their pixmaps.

someone really has to sit down with the GTK and Gnome libraries and start optimizing them for size and speed

Another example of the shared memory bug in top is in libraries. Under Linux, a library's code segment is marked read-only; it can be shared among several processes, making top misreport the memory the library is actually using.

I disagree about the bit that Gnome sucks in 8 bit. Actually it must do something right: when I run Mozilla under plain IceWM with lots of other color-intensive apps loaded (e.g. RealPlayer), it's too ugly too look at.[1]
However when I run it under Gnome + IceWM, it looks just about OK (even with Modern skin)! I can't imagine why this is, but I won't complain if all I can have is this Ultra 1 workstation I use at the university... [1] see bugzilla, please vote for this one!

Bugzilla, OTOH, is more full-featured (too full-featured for most small dev groups, IMHO) and uses a SQL database. So you could theoretically run just about any report you like. I don't think it records all the bug dates you'd need for the reports you mentioned, but that's a relatively trivial patch.

I would then try to browse the source with a hyperbolic web visualization tool, such as Inxight or Webviz from the Geometry Center (RIP). Apparently there are many such visualization tools. Perhaps one will work well with LXR output.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

Mozilla .7 was still to bloated to run at home, after installing the jvm. Personally I think that the jvm that they are using sucks butt. It launches about 30 threads that just take up all my memory. Why????

There is a bug reported about JavaPlugin been loaded at statup. (bug 26516). And there are people working on it.

There are people working on startup performance.

• Bug 18277 - Need to lazily load the OJI DLL
• Bug 27510 - Too much read from disk on startup
• Bug 29063 - Excessive stat calls
• Bug 29249 - 49 dlls loaded on startup: 50% of startup time

And there are many reports about performance in general that are beeing addressed (Performance problems)

I hope someday Mozilla will be the Browser of our dreams. We can all help this to happen by reporting bugs, correcting them, or promoting Mozilla project.

The important thing to remember is that all of the recommendations fit together. You can take just one (simple design, comprehensive unit testing), apply it to your work, and see some benefit. If you use all of them together, the interactions will give you more benefit.

If you avoid the tenets of 'simple design' and 'reduce complexity', you'll have lots of trouble testing things. You'll spend lots of time debugging complex interactions between components.

However, if you decouple things, test aggressively, and use simple and sane interfaces whenever possible, you'll have less difficulty. It's not a magic bullet, but simplicity really is a virtue in this case.

Finally, the idea that change is always more expensive in the future is a very pervasive belief in software engineering. I'm not so sure. I can't back it up, but I'm willing to bet that projects like the Gimp, Mozilla, and even Apache have spent or will spend more on their ground-up rewrites than they would have spent refactoring and simplifying. (Heck, I'd pay money to get a set of unit tests with a web browser!)

I have no way to prove that. Then again, that CS professor who said "It will cost more to change things in the future" couldn't prove it either, and I know he'd never worked with requirements that changed every two months.

At least in the software I'm writing where I can use XP, it's helping.

--

Correct me if I am wrong, but isn't this exacly what the mozilla project's Tinderbox and smokering test do?

Accountability is important when code breaks. =)

-pos


The truth is more important than the facts.

Fizzilla is here.

release a version that could handle css better

Recent Mozilla supports CSS stylesheets, and it supports them well. Or are you trying to make a combination DVD player/set-top Web terminal? In that case, you'll need to get your CSS elsewhere.

or didnt fail because some piss poor coder forgot to close off a table

Not only is the HTML invalid in that case, it isn't even well-formed, and (once the stricter XHTML standard becomes widespread) most browsers will throw up an alert box for that. Note that even in Slashdot and Kuro5hin comments, I use a </p> for every <p> .

The version 6 is so freaking bloated

The release labeled as "Netscape Communicator 6.0" is bloated with AOL brand clutter. If you download a Mozilla brand milestone such as 0.7, it'll be almost as fast as the Netscape 4.5 you're currently using.

release a version that could handle css better

Recent Mozilla supports CSS stylesheets, and it supports them well. Or are you trying to make a combination DVD player/set-top Web terminal? In that case, you'll need to get your CSS elsewhere.

or didnt fail because some piss poor coder forgot to close off a table

Not only is the HTML invalid in that case, it isn't even well-formed, and (once the stricter XHTML standard becomes widespread) most browsers will throw up an alert box for that. Note that even in Slashdot and Kuro5hin comments, I use a </p> for every <p> .

The version 6 is so freaking bloated

The release labeled as "Netscape Communicator 6.0" is bloated with AOL brand clutter. If you download a Mozilla brand milestone such as 0.7, it'll be almost as fast as the Netscape 4.5 you're currently using.

use this.

And the checking is damn strict: one syntax error and all you see on the phone is 'invalid tag'. It would be nice if some popular browsers did that.

That's why I really hope Mozilla gets the iCab-like feature discussed in bug 6211. And I hope they put it right smack dab obvious in the UI like iCab, too.

In the real (i.e. commercial) world, in most cases it is not worth supporting Netscape or MacOS.

But it takes even more effort to exclude them than it would to simply let them in and see the crap that you couldn't be bothered to clean up.

Of course, we need to develop applications that work on browsers on PCs, WAP phones, STBs and suchlike, but no-one can afford to support every possible platform and configuration.

Get some decent tools, then. You know, one that produce valid HTML 4.01 Strict, and valid CSS2 to go along with it. Ones that don't let you set fixed sizes for fonts. You know, so that the design philosophy of "graceful degradation" would actually be realized, and the web would be accessible to everything. If there was just one decent tool like that to use, it would take no more effort than it currently does. Maybe Mozilla will come with a decent authoring tool. I bet the folks at Opera could do it if they wanted to.

I think this idea is very good. I think that most of the comments agree on one thing though : Stallman's article doesn't give enough details on the practical side to make it seem real. He (as usualy) defends the ethical side of the problem, and rightly enough describes the way the content should be free (speech) but he leaves a huge blank area in the field of the practical (and technical) implementation of GNUpedia.

I think that Internet and the Open Source community is somehow ready to start such a project (and I don't think it was the case anytime before).

What we need to make it real is a deep deep thinking on the technical/practical side of it. And while we are here, why not talk about how you would technically do it ? I mean, /. readers are probably the most qualified to talk/think about this if not to implement it themselves...

Here is how I would see it : I think that what we realy need in terms of encyclopedia is something that would sit between Shaslcode and QuestionExchange. Something where anyone could post comments, articles, pictures and all the shit, but where every willing people could also judge the pertinence of the content. Say for example that this article is a troll, this other one is "insightfull" and so on. People could also say "this article was usefull to my knowledge". So we would have two level of moderation : one on the "editorial scale" (troll/interesting), and one on the content quality/usefullness.

Why ? Because I think that Stallman is right on one point at least : it needs to be completly free (speech) to be interesting. Doing else would be doing something that has already be done (say britanica for example) and that perhaps doesn't need to be done again.

Making GNUpedia an "open to any post" system is a nice idea, but it also implies that we will have to face A LOT of content submissions. Even if we wanted to create an "editorial board" to decide what would be included and what would not (which we cannot if we want to remain free as in speech) it would be too much work for (volunteers) individuals to "separate the good from the evil".

So what we need is a system that allows anybody to feed it with his/her particular bit of knowledge, and them let the individual reader make the content "worth reading" by moderating it up or down.

Then, after a while, we might (might) have something interesting for anyone. In that case I'm sure it would be the greatest success of Open Source movment (aren't we talking about free knowledge, free information since the very beginning of Open Source ?)

Another thought I have too : why make it web (http) based ? Any rational reason for it ? I think we have now in our hands a better technical way to do it : why not build it as a peer-to-peer network (based on this or that) with a client/server program using Gecko to render the documents ? What do you think ? That was my 2 cents worth thoughts...

PS : Please forgive the english, it's not my mother tongue.

Attach your page as a testcase to the bug to aid in performance tuning.

Thanks for making Mozilla a better browser. :)

It runs on every platform that Mozilla does: Windows, Linux, Solaris, HP, AIX...even Mac!

my friend at microsoft gave me this secret link to the mozilla CVS repository. :)

--

--

and obviously editing text in forms is as liable to human error as always

Sigh - the corrected url is:this one

There is also a newly updated RoadMap that includes possible dates for V1.0 before this Summer.

Seriously though, in NS 6 and Moz 0.6 there was a bug (45747) where Mozilla wouldn't work with MS Proxy 2.0 if NTLM was enabled (if you're interested in why, all the info is in the linked bug). This has since been fixed (it's been fixed in the nightlies for quite a while).

Actually, that's just some of what's new. That list highlights some of the features that users are likely to notice right off. For a more comprehensive list you might try a bugzilla query something like the 1500 or so bugs fixed since around Mozilla 0.6 It's not a perfect query since a few of those were in M18 and not in 0.6 and vise versa but you get the picture. --Asa

still slower than ns 4.x. Yes, netscape sucks, but it still appears quicker for me (1s) than mozilla (~2s) when clicked from the gnome panel. That's with an already running program btw, not from scratch.

Agreed. I'm on Windows and new window performance is the main thing preventing me from using Mozilla as my main browser (even though it's much more stable than IE).

From the Installation Notes:

Before installing on Linux, you must have write permission for the target installation directory. (Bug 46588)

So it's saying that I need +w in the install directory when I install Mozilla? No way!

--

From the Installation Notes:

Before installing on Linux, you must have write permission for the target installation directory. (Bug 46588)

So it's saying that I need +w in the install directory when I install Mozilla? No way!

--

From the Compatibility Information:

For Red Hat Linux 7, you must install the Standard C++ libraries for Red Hat 6.x compatibility. Get the package from the Red Hat 7 installation CD or download it from Red Hat. (Bug 59012)

--

From the Compatibility Information:

For Red Hat Linux 7, you must install the Standard C++ libraries for Red Hat 6.x compatibility. Get the package from the Red Hat 7 installation CD or download it from Red Hat. (Bug 59012)

--

please make sure the bugs also occur in a recent nightly build. Mozilla 0.7 branched about two weeks ago so your bug might have been fixed since then.

By the way, today's nightlies are pretty good - several recent regressions were fixed. Two new bugs in today's builds that weren't in 0.7: links on some pages are ignored and home page isn't displayed on startup under Win32 when using -console option.

please make sure the bugs also occur in a recent nightly build. Mozilla 0.7 branched about two weeks ago so your bug might have been fixed since then.

By the way, today's nightlies are pretty good - several recent regressions were fixed. Two new bugs in today's builds that weren't in 0.7: links on some pages are ignored and home page isn't displayed on startup under Win32 when using -console option.

please make sure the bugs also occur in a recent nightly build. Mozilla 0.7 branched about two weeks ago so your bug might have been fixed since then.

By the way, today's nightlies are pretty good - several recent regressions were fixed. Two new bugs in today's builds that weren't in 0.7: links on some pages are ignored and home page isn't displayed on startup under Win32 when using -console option.

From the Compatibility Information:

If you are using an ATI Rage video card, images are correctly displayed initially, but may not be properly re-drawn when you minimize and maximize or resize the window.

--

Release notes are here. FWIW, though, I still prefer the daily builds :).

Alex Bischoff
---

Release notes are here. FWIW, though, I still prefer the daily builds :).

Alex Bischoff
---

but just in case, for those who do not go there often, dozens of mirrors are listed here:

http://www.mozilla.org/mirrors.html

I am really looking forward to this, because NS and moz0.6 have been just a little bit problematic for me. Little things, like go to page x then open a new window go to page y, and it thinks it is still on page x. Infuriating, but what can I say.

I have great hopes for this.