mad jew said:
ya, saw that one... I was going to ignore that one for now
my thought is that sometimes strange Ad code can cause rendering issues, but it wouldn't affect the contributors since there are no ads for them.
arn
mad jew said:
mad jew said:Most of the times it's happened to me today (probably thirty, forty or so times) it has been when I'm opening a new thread in a new tab. It's no huge hassle, but it's pretty weird.![]()
mad jew said:Most of the times it's happened to me today (probably thirty, forty or so times) it has been when I'm opening a new thread in a new tab. It's no huge hassle, but it's pretty weird.![]()
First one I've heard anyone mention.mad jew said:Is that the first Firefox incident?
Nah... I've seen a few using Firefox 1.5, but just assumed it was my browser that was acting up. But it's the first I've seen with 2.0 and the first one after this thread was started.mad jew said:Is that the first Firefox incident?
Yeha, if firefox would check my spelling, I'd switch over. But as you can see, I'm very likely to type things like yeha instead of yeah so I need the spell checker. (And I actually did type yeha inadvertently in that first sentence. And just had to get Safari to spell inadvertently for me. Twice.)Mitthrawnuruodo said:gotta love Firefox...![]()
Mitthrawnuruodo said:I've just seen bad renderings exactly like the one attached a couple of post up, where the odd (short) post has been affected. Not seen anyone more messed up than that, and nothing even close to some of the horror screen shots from earlier in this thread... gotta love Firefox...![]()
Firefox 2.0 has built in spell checking, while for the latest 1.5 you need Spellbound development version. Both of them supports a lot more languages than Mac OS X' built in spell check, so I have UK English and Norwegian spell checking in my browser...Heb1228 said:Yeha, if firefox would check my spelling, I'd switch over.