Planning For Mozilla 2.0
wikinerd writes "The MozillaWiki maintains a number of pages on Mozilla 2.0 which reveals lots of possible new features of the popular browser. What does your wishlist include about Mozilla 2.0, and how has the release of Firefox affected your use of Mozilla?"
Plus, Firefox seems quicker and more stable to me since I have been using both.
The problem is not Mozilla. The problem is Slashdot's piss poor HTML.
Join the Free Software Foundation
This has been fixed in the trunk for a long time (but not the branch Firefox 1.0 comes from), and will be in Firefox 1.1, whether Mozilla increments to 2.0 or not.
Bug 217527
Bug 264913
If you really, really need a fix now, visit this URL and download one of the nightlies from the trunk [fair warning - some nightlies have some annoying bugs in them, but generally, are pretty good]. It works just fine there, but I'm told requires too many changes to backport into the ff1/mozilla whatever branch.
There may be some I missed. In other words, you can install Mozilla with just the browser. However, you have to compile it for yourself if you want that.
I've come for the woman, and your head.
Slashdot rendering bug was fixed too late for firefox 1.0. It's going to be in version 1.1 (march) or if you cant wait download a nightly ( here http://ftp.mozilla.org/pub/mozilla.org/firefox/nig htly/ )
Try Chris Pederick's developer toolbar - built in validator plus a bunch of other bits. I love it, makes my job lots easier :-)
Greg
(Inside a nuclear plant)
Aaaarrrggh! Run! The canary has mutated!
Slashdot does have piss-poor HTML, but there's also a minor Gecko bug (see https://bugzilla.mozilla.org/show_bug.cgi?id=21752 7) which is why it works fine in other browsers.
A List Apart did an article on how to fix it but nothing seems to have happened.
Guy asked me for a quarter for a cup of coffee. So I bit him.
You can download an HTML validator for Firefox that builds it right into View Source. It will validate it within the browser and also provide accessibility warnings. It's based on Tidy.
- jiggity
Nope, not true. It's a Mozilla problem with relative table sizes. It simply calculates the distribution the wrong way (before the end of the document load), so it can only render the page properly if it's on the cache.
Your head a splode