> I can't see any trace of it in edge either (or even a comment > explaining a similar fix). > A cursory inspection with tcpdump and a current version of Safari > suggests it is no longer a problem (According to the changelog the > original fix dates back to 2005) and so perhaps this was just removed > because affected versions of Safari are effectively dead?
I've yet to see strange bugs on any of my ajax-using-edge-apps, so perhaps it's unneeded going forward. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
