> Thank you, Dmitriy! Works like a charm! Now I'm chasing a non-related
> IE-specific JavaScript bug (sigh). Hugi, please pay the beers you owe me to
> Dmitriy! :D
Sure — just have him contact me next time he's here in Reykjavik, Iceland (yes:
that's how I can afford to promise beer to everyone
Thank you, Dmitriy! Works like a charm! Now I'm chasing a non-related
IE-specific JavaScript bug (sigh). Hugi, please pay the beers you owe me
to Dmitriy! :D
On Mon, 19 Dec 2011 15:07:10 -0200, Dmitriy Vsekhvalnov
wrote:
I do.
I'm using tapestry-js-fixes.js (i'm not sure where did i ge
i include: tapestry-js-fixes.js in my Layout component, which is used in
every my page. May be not best approach, but it works.
And i also have following lines in my AppModule:
//prototype 1.7 support
public static void
contributeFactoryDefaults(MappedConfiguration configuration)
I do.
I'm using tapestry-js-fixes.js (i'm not sure where did i get it, so content
inlined)
== tapestry-js-fixes.js =
Tapestry.ZoneManager.addMethods({
processReply : function(reply) {
Tapestry.loadScriptsInReply(reply, function() {
/*
* In a multi-zone update, the reply.cont
Hi!
Has anyone tried to use T5.1.0.5 with Prototype 1.7 and Scriptaculous 1.9?
I'm having some weird JS errors:
* Tapestry.Logging not defined.
* Tapestry.Messages not defined.
* undefinedTypeError: reply.zones is not an object.
Are there known Tapestry.js issues with these versions of Protot
