For your information, here's a comment from the main DOM engineer of Mozilla (from bug 74201 WONTFIX)
If it would've been decided in the early days of mozilla that document.all
should be supported then I wouldn've have much problem with doing so, but
deciding now to start supporting document.all is IMO a very bad idea, there are
pages our there already that use code like:
if (document.all) {
// Do IE specific stuff
} else if (document.getElementById) {
// Do mozilla specific stuff
}...
and if we'd now all of a sudden started supporting document.all we'd break
things like this.
Even worse, the closer to IE mozilla gets (in terms of DOM functionality) the
more bugs we'll get about mozilla not working exactly as IE does, and I'm not up
for revers-engineering everything in IE at this point, that would be extremely
complicated and time consuming. We're already seeing similar problems with
mozilla's support for IE's element.offsetXXX properties, they behave more or
less the same way, but not exactly what IE does, and finding out exactly how IE
works is non-trivial (for all the hundreds of proprietary methods/properties in
IE), to say the least.
I'm all for implementing functionality in mozilla that exists in IE and is very
useful, cleanly defined and has a nice clean API, however, document.all is not
one of those things, I it's not a clean API (it's a list and a hash and callable
function, and what exactly does it contain? Who knows?), there are other nice
clean standards compliant API's that give you everything that document.all gives
you, I say that's enough.
Marking WONTFIX.
Re:Java incompatible with Netscrape 4.7x
on
Mozilla 0.9.5
·
· Score: 1
Three different bugs about Lotus Domino server:
bug 87782
bug 101899
bug 103147
>IE6 kicks the shit out of Mozilla at cookie-handling
This is not my experience. Can IE show you all cookies on your hard drive separately, that you can remove one by one. Can it give you the host, the name, the expiration of each cookie separately? Oh no, IE can block third-party cookies! Well, Mozilla has a nice pref called "Enable cookies for the originating web site only" that does exactly this (and it's what I'm using). No really, I don't see how IE is superior wrt cookies.
I'm not saying it's not a memory hog, but it's very very far from 120MB. When I first launch it takes about 20MB, IE 10MB, but we all know why.
A usual browsing session takes me to 30-35MB, which imho is not overexagerated, compared to what it used to be, and given that I have plenty of RAM:)
You have to read what top says very carefully. It will often display four or five instances of mozilla-bin that take each 35MB. In fact it means Mozilla is using all in all 35MB since they use the same memory. You don't have to sum them up.
It will be in Mozilla0.9.1. The back end is there, at least, they're working on the UI.
Re:you've fallen for MS strategy
on
Mozilla 0.9 Out
·
· Score: 1
Talk about desinformation.
The XSLT engine (Transformiix) will be in mozilla0.9.1. It was almost there for 0.9 but build issues have pushed it to the next milestone.
I don't think there are currently any plans to implement the XML Schema though, unless I'm mistaken.
Fabian.
Re:When will the import util handle Netscape Mail?
on
Mozilla 0.9 Out
·
· Score: 1
The only way to import Netscape Mail is to import your Netscape profile through the profile manager
(mozilla -profilemanager)
Fabian.
Re:Still pretty disappointing...
on
Mozilla 0.9 Out
·
· Score: 1
Yes we are very sorry for the poor state of the bookmarks manager at this point. In the nightlies you can now delete bookmarks again, and we will try to focus on bookmarks more for 0.9.1.
Fabian.
Re:How to stop popup windows?
on
Mozilla 0.9 Out
·
· Score: 1
Go to Help> Release Notes then click on the Mozilla0.8 release notes. Scroll down a little and you will see how to do it.
If you find a *real* bug in Mozilla's style system, please file it in bugzilla.mozilla.org. But rest assured that it will most likely be sent to the evangelism component, for improper use of the CSS standards. Your CSS has probably been coded for IE, and a few tweaks here and there (to make it standard of course) should make it work both in Mozilla and IE.
I can only answer the second part of the question:
Some Mozilla developers are lucky enough to work for a company that pays them to hack on Mozilla. Examples are Netscape, IBM, Sun, ActiveState, etc. It happens that the person who rewrote the image library works for Netscape and so he gets "compensated".
On the other hand some developers are real open source developers, meaning they do it in their spare time. For those (like me), the only and best reward is to watch the software evolve and become better and better.
I'm not sure about the CD's etc, but I would say yes, at first sight.
Please try the following:
Remove the file called "user-skins.rdf" in the chrome subdir of your profile directory. Then restart Mozilla. This will cause the default theme to be used and most of the time this fixes the crashes on startup.
Please read the Release Notes. Around the middle of the page there is a "fonts" section with two links to a site that shows you how to modify Mozilla fonts. You can also look at http://www.mozilla.org/unix/customizing.html if you could not find what you needed.
Hope this helps!
Slashdot Mirror
If it would've been decided in the early days of mozilla that document.all
should be supported then I wouldn've have much problem with doing so, but
deciding now to start supporting document.all is IMO a very bad idea, there are
pages our there already that use code like:
if (document.all) {
} else if (document.getElementById) {
}
and if we'd now all of a sudden started supporting document.all we'd break
things like this.
Even worse, the closer to IE mozilla gets (in terms of DOM functionality) the
more bugs we'll get about mozilla not working exactly as IE does, and I'm not up
for revers-engineering everything in IE at this point, that would be extremely
complicated and time consuming. We're already seeing similar problems with
mozilla's support for IE's element.offsetXXX properties, they behave more or
less the same way, but not exactly what IE does, and finding out exactly how IE
works is non-trivial (for all the hundreds of proprietary methods/properties in
IE), to say the least.
I'm all for implementing functionality in mozilla that exists in IE and is very
useful, cleanly defined and has a nice clean API, however, document.all is not
one of those things, I it's not a clean API (it's a list and a hash and callable
function, and what exactly does it contain? Who knows?), there are other nice
clean standards compliant API's that give you everything that document.all gives
you, I say that's enough.
Marking WONTFIX.
Three different bugs about Lotus Domino server:
bug 87782
bug 101899
bug 103147
Just wanted to say thanks for keeping us from working with our main tool, Bugzilla. I hope we don't have to suffer this again in the future.
-Fabian.
This is not my experience. Can IE show you all cookies on your hard drive separately, that you can remove one by one. Can it give you the host, the name, the expiration of each cookie separately? Oh no, IE can block third-party cookies! Well, Mozilla has a nice pref called "Enable cookies for the originating web site only" that does exactly this (and it's what I'm using). No really, I don't see how IE is superior wrt cookies.
Fabian.
I'm not saying it's not a memory hog, but it's very very far from 120MB. When I first launch it takes about 20MB, IE 10MB, but we all know why. A usual browsing session takes me to 30-35MB, which imho is not overexagerated, compared to what it used to be, and given that I have plenty of RAM :)
You have to read what top says very carefully. It will often display four or five instances of mozilla-bin that take each 35MB. In fact it means Mozilla is using all in all 35MB since they use the same memory. You don't have to sum them up.
Mozilla has had java support for a long time now. Just download the jre.xpi from java.sun.com and you're done.
It will be in Mozilla0.9.1. The back end is there, at least, they're working on the UI.
The XSLT engine (Transformiix) will be in mozilla0.9.1. It was almost there for 0.9 but build issues have pushed it to the next milestone. I don't think there are currently any plans to implement the XML Schema though, unless I'm mistaken.
Fabian.
Fabian.
Fabian.
Fabian.
Fabian.
On the other hand some developers are real open source developers, meaning they do it in their spare time. For those (like me), the only and best reward is to watch the software evolve and become better and better.
I'm not sure about the CD's etc, but I would say yes, at first sight.
Fabian.
Remove the file called "user-skins.rdf" in the chrome subdir of your profile directory. Then restart Mozilla. This will cause the default theme to be used and most of the time this fixes the crashes on startup.
Fabian.
Please read the Release Notes. Around the middle of the page there is a "fonts" section with two links to a site that shows you how to modify Mozilla fonts. You can also look at http://www.mozilla.org/unix/customizing.html if you could not find what you needed. Hope this helps!