Rails spinoffs - May 2007 - Safari 1.3.2 (perhaps all of 1.*) and Prototype ajax.Updater function?

Hey folks -

I''ve got some Prototype functions that seem to work like a champ on IE
and FF - but testing in Safari 1.3.2 (no OS X Tiger here yet - but a
friend with Safari 2 had no problems) crashes the browser.

I''ve been tinkering with my code, and found that the culprit seems to
be the ajax.Updater function. The following (pseudo-code) breaks
Safari:

var ajax = new Ajax.Updater(
	{ success: ''myDiv'' },
	url,
	{
		method: ''get'',
		parameters: '''',
	});

but the following ajax.Request bit works ok:

var ajax = new Ajax.Request(
	url,
	{
		method: ''get'',
		parameters: '''',
		onComplete: function(t) { $(''myDiv'').innerHTML =
t.responseText; }
	});

Has anyone else come across this sort of issue? And if so, is there a
workaround to properly use the "Updater" functionality as opposed to
having to go the "Request" route?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Hey Scott, did you ever come across an answer to this?

Looks like I''ve run into the exact same issue with Safari 1.3.2:
http://www.librarything.com/talktopic.php?&topic=12551

I''ve switched it to use Ajax.Request, like you suggested, but if the
root cause is still undetermined, makes sense to me to just avoid
Ajax.Updater from now on.  A bug that *crashes* a browser is pretty
serious, and it''s not like Request+oncomplete is terribly verbose,
compared to Updater.

Altay



On May 3, 11:43 am, ScottW
<sweik...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Hey folks -
>
> I''ve got some Prototype functions that seem to work like a champ
on IE
> and FF - but testing in Safari 1.3.2 (no OS X Tiger here yet - but a
> friend with Safari 2 had no problems) crashes the browser.
>
> I''ve been tinkering with my code, and found that the culprit seems
to
> be the ajax.Updater function. The following (pseudo-code) breaks
> Safari:
>
> var ajax = new Ajax.Updater(
>         { success: ''myDiv'' },
>         url,
>         {
>                 method: ''get'',
>                 parameters: '''',
>         });
>
> but the following ajax.Request bit works ok:
>
> var ajax = new Ajax.Request(
>         url,
>         {
>                 method: ''get'',
>                 parameters: '''',
>                 onComplete: function(t) {
$(''myDiv'').innerHTML = t.responseText; }
>         });
>
> Has anyone else come across this sort of issue? And if so, is there a
> workaround to properly use the "Updater" functionality as opposed
to
> having to go the "Request" route?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Am 11.05.2007 um 08:01 schrieb altay-6c8tSettBfPPIjl8wruziA@public.gmane.org:
> A bug that *crashes* a browser is pretty serious
Yes, not _this_ much for Prototype, but for the browser, as this is a  
potential security issue. While I guess there is no hope that Safari  
1.3 will receive further patches from Apple, I do hope Safari 2 will  
get the updated rendering engine Safari 3 has once that one is  
released (more or less the same thing happened with Safari 2 and  
Safari 1.2).

Safari 2 also has it''s share of browser-crashing things, especially  
the RegExp engine is vulnerable.

Anyway, back on Topic:

Can anyone with Safari 1.3 make please submit a patch for this?

Best,
Thomas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Thomas, thanks for the reply, and thanks for all your web app
innovations!

I''d be happy to help with a patch... but, unfortunately, I
don''t have
access to Safari 1.3.  My report came from a user.

But I''ll take a look at the tickets/wishlist to see if I can help out
with anything else.

Altay


On May 11, 6:17 am, Thomas Fuchs
<t.fu...-moWQItti3gBl57MIdRCFDg@public.gmane.org>
wrote:
> Am 11.05.2007 um 08:01 schrieb
a...-6c8tSettBfPPIjl8wruziA@public.gmane.org:
>
> > A bug that *crashes* a browser is pretty serious
>
> Yes, not _this_ much for Prototype, but for the browser, as this is a
> potential security issue. While I guess there is no hope that Safari
> 1.3 will receive further patches from Apple, I do hope Safari 2 will
> get the updated rendering engine Safari 3 has once that one is
> released (more or less the same thing happened with Safari 2 and
> Safari 1.2).
>
> Safari 2 also has it''s share of browser-crashing things,
especially
> the RegExp engine is vulnerable.
>
> Anyway, back on Topic:
>
> Can anyone with Safari 1.3 make please submit a patch for this?
>
> Best,
> Thomas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Still no luck with Safari 1.3.2 and Ajax.Updater. I''ve redone all my
code to use Request/onComplete instead.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---