Slashdot Mirror


Meet The Co-Creator of Firefox

Jay Langhurst writes "Learn more about the roots of Firefox and about the 19-year-old who co-created the browser in this article. 'To take an internship at Netscape during the summer of 2001, Ross moved with his mother to a rented apartment near Netscape's offices in Mountain View, Calif. She drove him to work each morning.'"

7 of 255 comments (clear)

  1. Re:But... by Anonymous Coward · · Score: 3, Informative

    It does in Firefox nightly development builds, and it will in Firefox 1.1, which should be out in a couple of months or so.

    Of course Slashdot could get a code cleanup before then...

  2. Re:But... by Malc · · Score: 4, Informative

    Haven't you been paying attention? Go and Google and you will learn that it was fixed in the mainline long ago, and you will also learn why it wasn't rolled in to FireFox 1.0.

    *sigh*

  3. Re:But... by almostmanda · · Score: 5, Informative

    This might be band-aiding the situation, but I haven't had to deal with the /. rendering probs since I downloaded the Slashfix extension.

  4. Re:But... by the+unbeliever · · Score: 4, Informative

    because slashdot spits out garbage HTML that doesn't fit even the most lax of validation checks.

    slashdot's html was written back in 1997ish, and hasn't been updated since.

  5. Re:Wired Mag Feb '05 cover - "The Firefox Explosio by digitalgimpus · · Score: 2, Informative

    The Wired cover is available here:

    Wired.com

    It's posted, just not linked up.

    Per Asa Dotzler's blog

  6. Re:But... by CTho9305 · · Score: 2, Informative

    It doesn't matter whether the HTML is garbage - it should render the same way every time you load it. However, there is a class of bugs in the gecko engine called "reflow" bugs, which only show up in certain situations, based on the timing of various events during page load, which sometimes cause the page to render differently.

    This *IS* a bug in Mozilla/Firefox, and it *HAS* been fixed for a long time (since before Firefox 1.0 was released) but the fix was not included in FF1.0 because it broke other things.

    For many reflow bugs, you can construct valid HTML that exposes it just as well as garbage "HTML".

  7. Re:But... by kaladorn · · Score: 2, Informative

    Depends what you mean by winning. If the new generation of gecko browsers drive MS into upgrading their security, adding tabbed browsing, and a host of other things that the 'others' now do, then really, the war will be won. Some people think the point is to get rid of M$. The truth is, the point is to get better software out there for everyone. And in that sense, Firefox and the others can make this a reality.

    --
    -- Mal: "Well they tell you: never hit a man with a closed fist. But it is, on occasion, hilarious."