Isn’t 12.0 something like quadruple-beta of the “Stable” version of Chrome? Maybe you shouldn’t be surprised.
I mean, I use Nightly, the triple-beta of FF because it has a 64-bit version (And let’s be honest here, I like feeling superior to to people) but whenever I get an error, I chalk it up to using an experimental browser and move on (or switch browsers.)
That being said, Nightly works far better than I would have expected for a highly experimental browser, even considering that it doesn’t support Java or Silverlight.
OP: For the record, I’m on Chrome 13 and I haven’t noticed anything like you mentioned here. The graphical glitches make me think something is up with your video card or the drivers for it, but if it’s only happening for LW...I’m not sure what to tell you.
Isn’t 12.0 something like quadruple-beta of the “Stable” version of Chrome? Maybe you shouldn’t be surprised.
I mean, I use Nightly, the triple-beta of FF because it has a 64-bit version (And let’s be honest here, I like feeling superior to to people) but whenever I get an error, I chalk it up to using an experimental browser and move on (or switch browsers.)
That being said, Nightly works far better than I would have expected for a highly experimental browser, even considering that it doesn’t support Java or Silverlight.
I’m not entirely sure what you mean here. It’s the current stable release
OP: For the record, I’m on Chrome 13 and I haven’t noticed anything like you mentioned here. The graphical glitches make me think something is up with your video card or the drivers for it, but if it’s only happening for LW...I’m not sure what to tell you.
Ahh, I guess it is. It’s been a long time since I used Chrome, I thought they were around 8.0 or 9.0.