Thread:Talk:Compatibility/Update A-grade browser support/reply (2)

Updating the document isn't going to break anything. I'm simply proposing to make it reflect, what afaik is, the status quo.

If most or all features work in those browsers, that's great. But that's not the same as being officially supported. It's not like things will be forced to break in those browsers, simply no systematic testing. Frontend features aren't been systematically been tested in Firefox 2, Safari 3 or older versions of Chrome right now, and haven't been in a long while.

It's not like people using browsers not matching this will get warnings of anything, nothing changes. Other than bugs reported for those browsers perhaps getting a lower priority, but then again, those bugs probably already are..

For what it's worth: jQuery is currently officially supported in "IE 6.0+, FF 3.6+, Safari 5.0+, Opera, Chrome". So for all we know certain jQuery features may already be broken in older browsers, and since we're using jQuery..