Anyone experience any issues using Prototype 1.6.0 and Rico 2.0 beta 3?
on 13.11.2007 15:43
on 14.11.2007 11:55
Yes,
I have found 2 issues:
1) Prototype 1.6 has a bug when converting a Hash to a query string.
Fortunately, it is easy to work around, just change 2 lines in
ricoLiveGridAjax.js:
from:
return $H(queryHash);
to:
return queryHash;
from:
Rico.writeDebugMsg('req '+this.requestCount+':'+
this.ajaxOptions.parameters.inspect());
to:
Rico.writeDebugMsg('sending ajax req #'+this.requestCount);
This change is also compatible with older versions of Prototype.
2) Prototype 1.6's implementation of "dom:loaded" is broken on Internet
Explorer. Unfortunately, there is no way to change a few lines of Rico
to work around this bug, but there is a ticket already created for
tracking it (http://dev.rubyonrails.org/ticket/10139). A code fix is
included in the ticket description and I have verified that it works
with Rico (requires changing prototype.js).
Therefore, I would recommend waiting until version 1.6.1 before
upgrading your Prototype library.
Matt
on 15.11.2007 21:38
I can confirm that this has fix has worked thanks. While I would love to avoid upgrading, there is a bug with Form.serialize() in previous versions of Prototype that we need fixed. Thanks for the help. Orion
on 16.11.2007 18:26
So, will the SVN include a patched version of Prototype 1.6?
on 19.11.2007 06:07
I have a strong preference for letting Sam Stephenson manage Prototype releases. What Richard Cowin and I have discussed (briefly) is releasing Rico 2.0 with Prototype 1.5.1 and planning a later Rico 2.1 release with Prototype 1.6.x. If Sam releases a 1.6.1 version quickly, I would be willing to include it in Rico 2.0. Comments? Suggestions? Matt
on 19.11.2007 14:14
My only concern is that other libraries such as scriptaculous have already begun depending on Prototype 1.6.
on 07.01.2008 15:38
The latest version in SVN now contains a patched version of Prototype 1.6. Please note that Prototype 1.6 also breaks Rico accordions on Opera. The version in SVN contains a patch for that too. Please give the latest SVN version a try and post back here if you find any other issues. Thanks, Matt


