in reply to Firefox occasionally not rendering nodes correctly

Actually, I find that Firefox is not breaking lines the way that some others do ... and the problem isn't the node you pointed out, but one of the replies, Re^2: Matching data against non-consecutive range. Actually, I had asked for an older node to be split via the consider option, and castaway sent me a note saying that it was split for her ... I guess it's not just me.

  • Comment on Re: Firefox occasionally not rendering nodes correctly

Replies are listed 'Best First'.
Re^2: Firefox occasionally not rendering nodes correctly
by Popcorn Dave (Abbot) on Jan 30, 2005 at 01:48 UTC
    That's sort of the problem I'm facing with Firefox. You're never quite sure which node is the culprit. Not that I'd trade back to IE. :)

    I installed Firefox on my parent's laptop and they're saying that it's faster than IE even on dial-up so something is going right. Now if it would just break lines where it's supposed to...

    Useless trivia: In the 2004 Las Vegas phone book there are approximately 28 pages of ads for massage, but almost 200 for lawyers.