John, if Safari 2 is not supported we are not sure the current method works as well. Is there any isolated test for globalEval and Safari 2? If there is then I agree it's not worth it to make it not usable anymore, otherwise the support.js could use a test case via .text property in the try catch and fallback into Function(data) for other browsers.
It is a little change that won't mean much, generally speaking, but since Opera 7.5, Safari 3, Firefox 0.9, MSIE 5 and every other starting from their first DOM support seem to be compatible, maybe we can assume script.text is a defacto standard, imho It's up to you, I am waiting for latest browsers there but Safari for Mac does not seem to be in the list anymore ... annoying! Regards On Sun, Nov 29, 2009 at 11:02 PM, John Resig <jere...@gmail.com> wrote: > > I can't tell you if it means it is not supported at all or if it ignored > or > > cause errors but AFAIK Safari 2 for Mac is not in the jQuery > compatibility > > list, is it? > > It's not in the compatibility list but we don't want to go out of our > way to intentionally break browsers either. As it stands the code > works, it could be simplified slightly (by only using .text) but if > it's at the expense of losing functionality for a browser then I don't > really think we should do it. > > --John > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
