Originally Posted by Recurring Villain
o rly
|
Yeah really. This was not a Safari issue, it was a site issue. I saw it using Safari, Pete saw it using Chrome, and even Jamie saw it using Firefox. Browser had nothing to do with anything.
And if it actually
were some kind of browser-specific site error, Safari actually displaying the error and bringing it to my attention would be significantly better for me and my users than Firefox's "ignorance is bliss" policy. So Safari + 2 in this particular case. One is just hypothetical but it gets a point for it anyway.
Originally Posted by Ross Hendrie
Firefox ftw...
|
Yes, Firefox ftw, and Safari ftmw.
Originally Posted by Jamie Minty
Thanks
|
You're welcome.