MozillaZine

Roadmap updated for Mozilla 0.9

Thursday April 19th, 2001

James 'kovu' Russell writes in:
"Mozilla.org recently updated the Mozilla Roadmap to reflect the crash landings that necessitated the 0.8.1 release. Groups embedding Mozilla are encouraged to target 0.9.1 for their beta branch point. 0.9.1 is currently slated for release May 25th."

The tree has closed for 0.9, so expect to start seeing 0.9 test build on ftp.mozilla.org next week at some time.


#23 Re: OUCH

by Nemo_NX

Saturday April 21st, 2001 11:39 PM

You are replying to this message

"Use standard coding practices..." well damn, tell that to Steve Gibson or all the other almost broke web masters who are trying to keep up their website any way they can. They got enough problems to deal with, you know that? Having a "standards compliant" website takes a lot of work to do. If IE does dthread tricks easier for people like Steve to code, then that's what he's going to do. He made a big deal about it last year and said that Netscape(4.x) was holding him back on doing some cool features like dthread, for example. So he decided to do it anyway without any Netscaope support(didn't even have anything to test with for Netscape, because Netscape 6 didn't come out yet), so now your telling him to redo all his custom made funky code for 10 percent or less of his viewers who still use Netscape. Um, that would be nice in a perfect world but that's not the case. Supporting HIS code would be better because it'll show that Netscape is trying to make life eaiser for the web masters. It's like adding legacy code to a new program like Windows XP has for Win 95 only programs. You support it to convenience people who don't have the time to redo everything. Now does THAT sound like a toatlly bad idea? We know the code is wrong but it's not our job to argue what kind of code web masters should use. Whatever they use(is more popular), is what needs to be supported. If standards compliate code is what they'll use then good for them, if not and they want to use IE only stuff because of better documentaion and it's easier to code then good for them too. Let them decide and not be forced to do it one way(IE only) then the other way(standards compliant) or people(like me, unfortunatly) will bitch to them to fix a problem that didn't exist before. There's too many websites doing it wrong so it's best not to make them look worse to force the web masters to "fix" thier webpage til it pleases those 'standards compliant' people. This is where I think Netscape is really screwing things up. Do you kind of understand where I'm getting at?

As for my insults at the Netscape programmers, this problem has been around since like what, M17? Taking time to get a problem right is okay, but these idiots are totally ignoring it. Meaning it will never be fixed. Never! Which is really sad because like you said, it's a good web browser. I see the 'future' tag which means this bug won't be assigned to any build before Mozilla 1.0. Yeah the big non-beta release. The moment in time people can really judge if Netscape 6 is junk or not. To not have that text box bug fixed by then is a real shame because now webmasters HAVE to CHANGE their webpages to make sure thier textboxs don't overlap on to other parts of the pages that it's not suppose to. I've seen this happen on <http://www.stomped.com> and they didn't fix it for like 2 months until they redid thier website. Now please give me one damn good reason why they have to do this? Why? Why deal with all the emails that will come in about a bug that's really Netscapes fault? When we are this close to having identical we pages in both IE and Netscape 6, this bug has got to be the most cruel form of punishment for both web masters and Netscape users. We EXPECT better than want we've seen so far.

"XML, JavaScript, and CSS" <-- dunno how to program in these languages. Wern't part of my IS program at college. Sorry.