MozillaZine

Site Suggestions

Tuesday January 8th, 2002

A few of you have asked for us to post a news item taking your suggestions for the site, so here it is. Tell us all your ideas for what we can do to improve the site. Anything you want we'll think about, but try to keep it realistic.

Just to keep you updated, one of the things we're planning on working on is getting the ChromeZone up again, if we can find some volunteer editors to help organize themes. If you're interested, please email me and I'll get back to you sometime this week.

UPDATE! Right now we're working on dumping all the tables and other old HTML within the site to both show off Mozilla's skills, and to get our file sizes smaller. If you're using Communicator to view the site, you'll notice everything looking pretty ugly, thanks to the poor CSS support it offers. If you're using IE, it'll look a bit better, but thanks to IE's lacking CSS2 support, the sidebar will show up incorrectly. We've completely redone the homepage and talkback code, and we'll be working on the forums next.

UPDATE 2! We discovered Google's great "Search Site" feature, and have added it. Right now it has most areas of the site indexed except news item talkback pages. It will start indexing talkback today, and will hopefully add all of the old items, in addition to picking up the new ones.

UPDATE 3! We've been working hard to get as many of your suggestions as possible implemented, and we encourage you to continue the feedback. You can check this article's responses for what items we have fixed, or are working on.


#103 The difference is standards.

by sacolcor

Sunday January 13th, 2002 7:15 PM

You are replying to this message

The difference is that ActiveX is a proprietary technology that belongs to one company, while CSS is an open standard developed by the organization in charge of defining the way the web works. I'll readily admit to being a purist rather than a pragmatist, but to me, once this site's pages are all made correctly according to the official HTML specs, then the problem becomes that IE is a broken browser, and complaints should be directed to Microsoft to support the specs properly, and not to the site owner for writing correct code.

Now, to take a more pragmatic tone, once the site has been brought up to W3C spec, if there are bandwidth and time efficient ways to make the site look better on IE6, they're probably worth looking into. Supposedly, it does support HTML4 and CSS1 pretty well, so there's probably a way to make it work on both.