On 7/10/07, Tobie Langel <[EMAIL PROTECTED]> wrote:
>
>
> Your post just triggered a commit (http://dev.rubyonrails.org/
> changeset/7170).
>
> Check SVN for the latest implementation.
Jeff, keep in mind that even this latest change still clobbers some native
methods. This is because the native o
Check Prototype 1.5.1 or 1.5.1.1 (the guts for that method don't seem
to have that problem)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to prototype-cor
Fantastic. I know breaking backward compatibility is never a good
thing, but I'm glad to hear that standards compliance is considered
just as important.
On Jul 10, 2007, at 3:38 AM, Mislav Marohnić wrote:
> On 7/10/07, Tobie Langel <[EMAIL PROTECTED]> wrote:
>
> Your post just triggered a co
prototype-1.5.1.1:
line 406:
unescapeHTML: function() {
return this.replace(/&/g,'&').replace(//g,'>');
}
but should be
unescapeHTML: function() {
return this.replace(//g,'>').replace(/&/g,'&');
}
Compare the results of
var string = '<';
On Snap!
Tricky, they define it again for WebKit and IE.
Follow the info here :
http://www.prototypejs.org/contribute
and create a ticket 8)
You can post back here with a link to the ticket if you wish.
--~--~-~--~~~---~--~~
You received this message because yo
> 1. Does the current API make sense? Was there anything about it that
> surprised you? Anything you'd add or remove?
Personally I am quite fond of the current API (for obvious reasons).
I especially like "Class.add" addition, although I think it might make
more sense represented as "Class.reop
