That was in 1999. Things have moved on since then:-)
As I understand it, the general recommendation is to use the +xml suffix when creating new MIME types - e.g. application/xhtml+xml (which, I believe, is currently going through the approval process as a MIME type). But it's also fine to send any sort of XML to a browser and expect it to style it using the style sheet you provide.
Gerv
It's not HTML, it's XHTML, which is an XML dialect, and so a text/xml MIME type is quite appropriate.
The reason the browser should know it's XHTML is that it has the XHTML namespace attached to the root element (html). Therefore, it should render it as XHTML, with the styles proposed both in the Link: header and also in the link tag in the body.
That's how I understand it, anyway. See here for the lowdown.
so what that we didn't fix a lot of the bugs for this milestone that were marked to be fixed?
This is part of the normal bug triaging process. Mangelo seems to find it very strange that we should prioritise bugs and decide which ones to fix now and which ones can wait.
a new milestone means a slip in the 1.0 release date,
This is another thing he keeps saying which is not true. It does not mean a slip in the release date, because we have no release date. New milestones get added to Bugzilla and the roadmap whenever we run out of the ones we've got. This action does not say anything about any dates.
People at MozillaZine knew about the story for a week and a half and tried to keep it secret.
They didn't try and keep it secret. It's not a secret - Mitchell's post to the public newsgroups shows that.
If you want a classic example of how mangelo writes untruths, how about "Netscape denies Netscape 6.1 is based on Mozilla source code"?
As soon as countries standardise on 00 as the international access code (and that's happening) then we will have a global unique numbering system administered by countries. It's called the phone system.
In the UK, we can already get "personal numbers" which you can have redirected to wherever you are. There's no reason why companies in other countries can't do the same thing.
That gives you all the benefits of unique personal numbering without many of the SSN/Big Brother/Brave New World/buzzword-X privacy concerns.
Er... why are you asking Slashdot rather than some, er, University IT Departments?
Here at Oxford, things are very decentralised. We have a crack team at the Computing Services (and our own version of CERT, OxCERT) who put emergency blocks on incoming mail if an email virus is doing the rounds (e.g. Kournikova) and manage the firewall between us and JANET, where some well-known and dangerous ports are firewalled out.
However, although we may have a site license for something (Sophos, I think) no-one's forced to use it. People are responsible for their own machines.
Why not just have a policy: "if your machine gets trashed by a virus and you didn't have this installed, we won't help you fix it." but not make it compulsory?
Sadly not. PGP isn't going to get into Mozilla any time soon because the Mail/News team want a pluggable architecture written first. They are the only people capable of writing it and they don't have time.
So, the guy from PGP Inc., who has written the PGP support (which works now) has been told his patch is a hack and won't be accepted.
There's a bug on this, but I don't have the number - search Bugzilla.
sea are usually the seamonkey builds from stable source.
This is incorrect. SEA stands for Self-Extracting Archive - it's an installer build. They are the same code as in the non-SEA builds, but with a proper installer. The tiny-sized builds are the net installer.
I'm probably wrong about this, but I think this version includes Talkback for automatic crash reporting. Either that, or it includes an installer along with the above tarball.
VMware has cool stuff like non-permanent disks so you can install it, see what happened, and then roll your disk back to where it was before the install. Just what you need.
Fixed positioned layers have always worked in Mozilla but do not work in Netscape 6.
They were disabled on the Netscape branch by agreement between Netscape and mozilla.org as part of mozilla.org's commitment to safeguarding web standards. The fixed positioning code had a number of bugs which would have plagued web developers trying to use fixed positioning in years to come. It was thought better just to turn it off.
If a non-profit cert company got set up with sufficient "trustability" (and that would actually take some serious legal doing) then their cert could be put in Mozilla. This may mean that it ends up in Netscape 6.x "by default" - as in, Netscape can't be arsed to take it out...
But I suppose "might" isn't good for a business model... on the other hand, the Mozilla organisation would almost certainly be sympathetic to any company wanting help to bring down the cost of SSL certs.
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."
My favorite thing about Christianity is that if God is all-knowing, then he already knows everything that's going to happen, including whether or not I'm going to accept Christ or not. And since God apparently created me, it's his fault if I don't.
That second sentence doesn't follow from the first. The fact that God is all-knowing doesn't preclude the possibility of you having free will. Whether you accept Christ or not is entirely your decision - you can't duck it like that.
Structured Programming, by O.-J. Dahl, E. W. Dijkstra, and C. A. R. Hoare has been continuously in print since 1972. It came highly recommended by Don Knuth, no less, in his recent lecture.
Slashdot Mirror
That was in 1999. Things have moved on since then :-)
As I understand it, the general recommendation is to use the +xml suffix when creating new MIME types - e.g. application/xhtml+xml (which, I believe, is currently going through the approval process as a MIME type). But it's also fine to send any sort of XML to a browser and expect it to style it using the style sheet you provide.
Gerv
It's not HTML, it's XHTML, which is an XML dialect, and so a text/xml MIME type is quite appropriate.
The reason the browser should know it's XHTML is that it has the XHTML namespace attached to the root element (html). Therefore, it should render it as XHTML, with the styles proposed both in the Link: header and also in the link tag in the body.
That's how I understand it, anyway. See here for the lowdown.
Gerv
so what that we didn't fix a lot of the bugs for this milestone that were marked to be fixed?
This is part of the normal bug triaging process. Mangelo seems to find it very strange that we should prioritise bugs and decide which ones to fix now and which ones can wait.
a new milestone means a slip in the 1.0 release date,
This is another thing he keeps saying which is not true. It does not mean a slip in the release date, because we have no release date. New milestones get added to Bugzilla and the roadmap whenever we run out of the ones we've got. This action does not say anything about any dates.
People at MozillaZine knew about the story for a week and a half and tried to keep it secret.
They didn't try and keep it secret. It's not a secret - Mitchell's post to the public newsgroups shows that.
If you want a classic example of how mangelo writes untruths, how about "Netscape denies Netscape 6.1 is based on Mozilla source code"?
Gerv
Please don't slashdot our Bugzilla server! Please! We need it, and currently it's dying.
Gerv
This is intentional. It's a joke. :-) The page is served as text/xml - its correct MIME type - and only Mozilla understands it correctly.
Gerv
As soon as countries standardise on 00 as the international access code (and that's happening) then we will have a global unique numbering system administered by countries. It's called the phone system.
In the UK, we can already get "personal numbers" which you can have redirected to wherever you are. There's no reason why companies in other countries can't do the same thing.
That gives you all the benefits of unique personal numbering without many of the SSN/Big Brother/Brave New World/buzzword-X privacy concerns.
Gerv
Er... why are you asking Slashdot rather than some, er, University IT Departments?
Here at Oxford, things are very decentralised. We have a crack team at the Computing Services (and our own version of CERT, OxCERT) who put emergency blocks on incoming mail if an email virus is doing the rounds (e.g. Kournikova) and manage the firewall between us and JANET, where some well-known and dangerous ports are firewalled out.
However, although we may have a site license for something (Sophos, I think) no-one's forced to use it. People are responsible for their own machines.
Why not just have a policy: "if your machine gets trashed by a virus and you didn't have this installed, we won't help you fix it." but not make it compulsory?
Gerv
Sadly not. PGP isn't going to get into Mozilla any time soon because the Mail/News team want a pluggable architecture written first. They are the only people capable of writing it and they don't have time.
So, the guy from PGP Inc., who has written the PGP support (which works now) has been told his patch is a hack and won't be accepted.
There's a bug on this, but I don't have the number - search Bugzilla.
Gerv
Their banner says "We decide problems of any complexity."
Wow. I wonder how they'd cope with the Halting Problem...
Gerv
sea are usually the seamonkey builds from stable source.
This is incorrect. SEA stands for Self-Extracting Archive - it's an installer build. They are the same code as in the non-SEA builds, but with a proper installer. The tiny-sized builds are the net installer.
Gerv
I'm probably wrong about this, but I think this version includes Talkback for automatic crash reporting. Either that, or it includes an installer along with the above tarball.
It's the installer.
Gerv
VMware has cool stuff like non-permanent disks so you can install it, see what happened, and then roll your disk back to where it was before the install. Just what you need.
Gerv
but it's been up for months. I remember reading it ages ago when he was still building the DNA Lounge.
;-)
Oh wait... he still is building the DNA Lounge. Good to see progress being made.
Gerv
I take it this book isn't much use to those of us who live outside the US?
I could really do with a book like this for UK law...
Gerv
Fixed positioned layers have always worked in Mozilla but do not work in Netscape 6.
They were disabled on the Netscape branch by agreement between Netscape and mozilla.org as part of mozilla.org's commitment to safeguarding web standards. The fixed positioning code had a number of bugs which would have plagued web developers trying to use fixed positioning in years to come. It was thought better just to turn it off.
Gerv
If a non-profit cert company got set up with sufficient "trustability" (and that would actually take some serious legal doing) then their cert could be put in Mozilla. This may mean that it ends up in Netscape 6.x "by default" - as in, Netscape can't be arsed to take it out...
But I suppose "might" isn't good for a business model... on the other hand, the Mozilla organisation would almost certainly be sympathetic to any company wanting help to bring down the cost of SSL certs.
Gerv
This despite three deadbolts on the tiny, 3-by-3 door leading to the roof and four other locked doors prior to reaching the top.
:-)
But, unless you leave someone on the roof permanently, 3 deadbolts aren't going to help much, because they'll be on the inside.
Gerv
The cache subsystem is being written to improve performance, stability and flexibility. Basically, the old cache sucked. Patience :-)
Gerv
2001-04-04 04:04:04 and here's some text to avoid the "lameness filter."
Gerv
SINS - SINS Is Not SSH :-)
SMERSH - Secure Multipoint Encryption Remote SHell (or something...)
Gerv
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
My favorite thing about Christianity is that if God is all-knowing, then he already knows everything that's going to happen, including whether or not I'm going to accept Christ or not. And since God apparently created me, it's his fault if I don't.
That second sentence doesn't follow from the first. The fact that God is all-knowing doesn't preclude the possibility of you having free will. Whether you accept Christ or not is entirely your decision - you can't duck it like that.
Gerv
Structured Programming, by O.-J. Dahl, E. W. Dijkstra, and C. A. R. Hoare has been continuously in print since 1972. It came highly recommended by Don Knuth, no less, in his recent lecture.
Gerv
The timebomb no longer exists, and hasn't for a long time. The page which mentions it should have been updated.
:-)
However, I would hope you find a build better than your current one inside 30 days
Gerv
You need MathML. Already available in special nightlies of Mozilla for Windows and Linux.
Gerv