Mozilla 1.2 Unleashed
asa writes "Mozilla 1.2 has just been released. New to this version are features like Type Ahead Find, basic toolbar customization (text/icons/both), support for GTK themes on Linux, multiple tabs as startpage,
Link Prefetching, "filter after the fact" and filter logging in Mail, Palm sync for Mozilla addressbook on MS Windows, and more. This is the latest stable release from mozilla.org, and all users of Mozilla 1.0, Mozilla 1.0.1, Mozilla 1.1 or any of the alpha/beta/release candidates are encouraged to upgrade to this release. You can get builds and more info at the Mozilla releases page and you can find daily Mozilla news and discussion at mozillaZine.org."
Number one is that there is no WYSIWYG editor for Mozilla.
Are you on crack, son?
If you are runing Mozilla, open up Composer. You now have a window where you can insert text, lists, headings, and tables and they will be rendered almost exactly how to you typed them. You should notice 4 little tabs at the bottom. "Normal" lets you edit your web page WYSIWYG style. "Show All Tags" shows you the same view as Normal, but with viewable HTML tags. "Source" gives you a listing of your HTML source, which you can hack on and have the changes updated in real-time in all of the other tabs. "Preview" shows you exactly how Mozilla renders the finished version of the page. It doesn't get any more WYSIWYG than this.
Second there is no support for drag and drop. There is drag and drop but not using onDrag and onDrop type of events which makes the programming extremely simple.
There is all kinds of support for DnD. Go to the address bar and you'll note that you can drag the link into the tab bar, bookmarks folders, and other places. Ditto for the personal toolbar. Last time I checked, Mozilla's DnD even worked just fine with Windows Explorer.
Third Mozilla for some reason is a little bit slow in Windows.
That doesn't surprise me, since everything seems a little slow in Windows. But when I've used Mozilla in Windows, I can tell you it beats IE hands-down on all of my machines. (Especially WinXP.) Now Moz does take a little while to start up, but enabling Quicklaunch fixes that.
But there is no point of having skins on the browser, it is totally stupid, useless.
Skins? Oh, you must be talking about themes. You aren't required to use customized themes. If you don't like themes, just pick Classic and never change it. Presto, everybody's happy. I will argue that themes are in fact not "totally stupid" and "useless." They are useful to a lot of people I know. I prefer the Classic theme because I'm not a big fan of pixmap themes... I like my interfaces simple. My friend likes the Grey Modern theme because he's a graphics and web page designer and it doesn't have any distracting colors when he's trying to perfect the color scheme of his pages/images. My mom uses the Pinball theme because she likes the way it looks and it gives her browser window more room to show the web page. Themes programs such as web browsers can be very useful. You want to talk about truly useless themes, you needn't look any further than the modern crop of fancy-pants MP3 players.
Mozilla on Mac OS X is somewhat joke. It doesn't feel like a native application.
It isn't meant to. Mozilla's interface is meant to be consistant across platforms, not consistant with the platforms it runs on. If you absolutely must have nothing but native-looking applications on your desktop, there are other web browsers out there that have the sole purpose of integrading with the native environment. Galeon, K-Meleon, Chimera, they're all there. Pick one and use that instead of whining that the Mozilla developers aren't bending over backwards to accomodate you instead of everyone else who uses the internet.
Mozilla's being standard complaint is good, however on the net lots of articles are written for IE, because of the historical reasons as we know it. So Mozilla should allow the users to make a nicer transition by enabling certain non-standard IE-only features as much as possible.
First of all, they're "web pages", not "articles." Second, most web pages are typically written for IE, not for historical reasons, but because web page designers use Windows and IE to design their pages. That won't change until they start to realize that Mozilla, in addition to being standards-compliant, is actually a great platform to develop web pages on since it includes a WYSIWIG/HTML web page editor, a DOM inspector, and a javascript debugger. Third, Mozilla does render web pages that would normally be broken because they don't follow standards properly. They render them in what's called a "Quirks Mode" which means that the renderer breaks a few rules and recommendations so that the page loads and displays. Pages that do follow the proper specifications get rendered in "Standards Mode" which enforces the HTML and other web standards as set forth by the W3C. Mozilla should definitely not support IE-specific extentions and features since that doesn't give web page developers any incentive to switch to Mozilla, but most importantly, it doesn't give them any incentive to write standards-compliant web pages which will work on *any* browser, even text or speech-based ones.
A chance to get laid?
example.org - powered by Linux!