Hello,
i am using ajax from prototype and some effects with scriptaculous and
i am getting a strange behaviour when it is to be executed in Internet
Explorer, my code use prototype history manager and for some reason my
contents isn't show in IE, the core of the javascript is listed below:
var
Le lundi 21 décembre 2009 13:05, T.J. Crowder a écrit :
You're just looking in the wrong place. The second parameter to the
onSuccess callback is the value of the X-JSON *header*, if any. It's a
means of sending back extra data alongside the main response. You're
sending JSON back in the
Hi,
I'm trying to use the BlindDown/Up effect but it it renders stuttery
and weird on all the major (FF 3.5, IE 8, Chrome 4) Browsers.
Basically, the background div that is is referenced in the function
call, doesn't extend all the way down. It's contents are shown fine.
Also, it works fine for
Hi T.J. Crowder
ajax-content is the only ID for the content element.
I am working with Prototype Version: 1.6.0.3 i will read and alter to the
proper usage of Class.create.
Ps.: ProtoHistoryManager is from one extension that i get in
http://scripteka.com/ (Prototype.HistoryManager)
Thanks
Nothing changed when i rewrite to not replace protoype in Class.create.
Any other sugestion to try ??
Thanks
2009/12/21 Glauber Portella glauberporte...@gmail.com
Hi T.J. Crowder
ajax-content is the only ID for the content element.
I am working with Prototype Version: 1.6.0.3 i will read
I updated my prototype and scriptaculous version and the problem didnt go
away.
I removed the history manager too to see if was a problem with it but it
wasn't.
Please help me!
2009/12/21 Glauber Portella glauberporte...@gmail.com
Nothing changed when i rewrite to not replace protoype in
Hi,
I'm afraid there's nothing much to do other than step through it in a
debugger (yes, there _are_ debuggers for IE, the script debugger[1]
and Visual Studio) and figure out at what point it's breaking. If you
can figure out where it's breaking and post that, we may be able to
help.
[1]
For most typical cases, JSON is easier, and more efficient. For one,
by sending a Content-type header of application/json you can send an
array down from the server, and Prototype automatically converts it
into a JSON object you can utilize.
Hope that's helpful. There are much better explanations
function show(){alert(get_data_default());}
This line will fail when you call show() because you're not passing a
function to fill the callback variable inside get_data_default().
Also, method:post and asynchronous:true are the defaults for those
options. You don't need to specify them if you
sorry for typing mistake, I am intended to represent the concept of
using callback.
and I think keeping default variable is not bad as we cant tell the
default value not to be changed in the next generation of prototype
js.
heeae
On Dec 22, 1:25 pm, joe t. thooke...@gmail.com wrote:
function
10 matches
Mail list logo
