http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thread/af4c707758c57973/8208e0fe9921b542
I originally posted to see if I was doing something odd that IE didn't
agree with. At first I thought it was the hash option, but I'm not
sure exactly.
I went back to 1.4 and started addin
> Yeah. Scripty could probably drop the Builder class once this gets into a
release
Or rather build upon it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send emai
On 5/1/07, Gareth Evans <[EMAIL PROTECTED]> wrote:
>
> I guess its similar to the Builder class, looking at your example, in
> scripty?
Yeah. Scripty could probably drop the Builder class once this gets into a
release.
--~--~-~--~~~---~--~~
You received this messa
Hi Mislav
Thanks for taking the time to provide a reply.
The new Element constructor will definitely be useful, and cleanly gets
around the createElement issue without altering the dom.
I didn't realise that prototype had a no dom method meddling policy, at
least not until I read #7744 and then i
On 5/1/07, Gareth Evans <[EMAIL PROTECTED]> wrote:
>
> Apologies, I actually searched and found #7744
> http://dev.rubyonrails.org/ticket/7744
>
> Gareth
>
Gareth,
The intention is good, but the idea - not so much. While Prototype does tons
of great stuff to built-in prototypes, adds methods and
