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."
That will fix it
First post, btw
i cannot help myself i want the f1rst p0st ...so bad
They would never admit this was a bug.
If this were an IE bug, you'd never hear the end of it. But since it's Mozilla, they'll find some way of justifying this. Let the silence begin!
1: Write free software.
2: ?
3: Fail to use DHTML on mozilla.
4: Profit!
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
...perhaps that's why there's still Microsoft ads on Slashdot...
When mozilla 1.0 got released we were all happy that it finally got there, but with so many bugs unfixed and more introduced it seems mozilla although good enough still lags. Themes aren't even back compatible anymore, pages in 1.2 don't render properly but in 1.1 they do - basically we don't know where the project is at and we don't know when it will get better. Maybe they don't have a good source control and accept and throw in patches submitted by anyone? This is a sure recipe for introducing new bugs.
John Ashcroft can kill who he pleases.
I actually tried and downloaded Mozilla 1.2.1 for Windows today. Having installed it on my computer, I tried going to some DHTML-based sites. However, I still keep getting the same error message as 1.2.0 :(
For example: this site won't work
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?
See this article in the google cache for the details on preferences: preferences.
good reference. I've bookmarked that one.
Mozilla finds the DHTML Bug in YOU!
Eat that are u MS bashers! Why don't u bash Mozilla for a change.
Quit Slashdot Today!
Like the mail-order bride I keep chained in my basement whom I regularly beat and jizz over.
However, you could have used a redirect link. Slashdot displays the domain name part of the URL between brackets, after your link, giving away all the fun. To avoid this, using one of the following fine redirectors:
- http://rd.yahoo.com/*<URL>
- http://www-cgi.cnn.com/cgi-bin/redir ?URL=<URL>
- http://www.fatwallet.com/redirect/bounce.php?<U
R L>
- http://g.msnbc.com/0ADP/sfdgsf.1?<URL>
- http://chkpt.zdnet.com/chkpt/auhql8/<URL>
- http://www.mattel.com/exitsite.asp?exitcode=mat
t el.com&url=<URL>
In these, substitute <URL> with the place where you want to lure the fish to.Happing trolling.