On Sep 25, 2006, at 9:03 PM, Naomi Carson wrote:

>
> elvelind pointed me to
> http://trac.turbogears.org/turbogears/ticket/1090, which  
> coincidentally
> fixes this as well.
>
> Sooo... no longer a problem! :)

The solution in that ticket doesn't implement the workaround that the  
code is currently doing for Safari... If someone can confirm that  
Safari now pays attention to the encodings of XMLHTTPRequests that  
come in (Safari 1.3 wasn't, and I don't think the first Safari 2.0  
was either), I'd say we get rid of the Safari-specific altogether.

Kevin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to