DHTML Bug Found in Mozilla 1.2
joyoflinux writes "The people at Mozilla have announced that Mozilla 1.2 contained a bug that caused sites that use DHTML to fail (more on the front page). They have pulled 1.2 from the releases page, pending a 1.2.1 release."
I know MSIE have exploits. Can't you just click the "Windows Update" button from the Start Menu, and when a new window prompts you for security verification, check the box "Always trust content from Microsoft Corporation" before you click the OK button, and then reboot. That should solve it.
With Linux/BSD/whatever, especially on Gentoo you need to recompile it from some source, and thus it reduces productivity.
Yeehaa for Windows!
Consider this, though. Retarded means (based on the italian root, or latin, whatever) "slower". So, to describe someone as Retarded means you're probably describing them in relation to yourself. Since the average windows user is "slower" than the average slashdot reader, it's safe to say that Windows lusers are retarded in a slashdot forum.
Like what I said? You might like my music
OK, maybe you're right about the fact that MSIE has more security flaws than other browsers. That's also because more people are using it and more people found bugs.
Still, Mozilla and Netscape will never be first class browser with large user base. Don't even think about commercializing Mozilla when it can't open certain DHTML sites. I've tried 1.2.1 (just now) on both Windows and my Debian.
They still have the same problems. The DHTML functionality hasn't been fixed. Bug #182253, "document.write() eats initial characters in 1.2".It explains why so many sites with DHTML menus are being hit by the current bug. The sites are using document.write() to create them.
Also, there is a new bug that was just recently discovered. Progressive JPEG rendering in Mozilla hasn't been functioning properly since release 1.2.1. As an example, this image will open properly in MSIE, Netscape 6 and 7, Opera, however it won't open properly in Mozilla.
So, what steps do you think that Mozilla developers to squash all these bugs?