Historically the JS libraries haven't seen enough patch volume to
justify the process overhead. I feel like we're turning the corner
there, though; we should probably start following the Report 12
process for Prototype. What does the rest of Core think?
Any message that proposes a new feature is
I feel like we're turning the corner
there, though; we should probably start following the Report 12
process for Prototype. What does the rest of Core think?
+1 ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Love the addtions to Effect.Shake. Applied.
Best,
Thomas
Am 14.10.2007 um 02:39 schrieb Ryan McGeary:
I've got one prototype patch and one scriptaculous patch awaiting
review from the core team. I went through the process of getting them
both reviewed and verified under the new Rails
Hello,
This is an issue that I've come across with the new rails 1.2.5
release, but I'm not sure if the problem lies within Rails, prototype
or scriptaculous. My testing seems to point more towards
scriptaculous, but I'm not sure and maybe somebody can explain this
one.
Looking at the two
Thanx xinze,
In the readme_first.txt file I point out that I had implemented some
patches from various tickets.
I goofed the patch on that one.
http://dev.rubyonrails.org/ticket/8843
should have been:
results.push($(query.snapshotItem(i)));
I will fix this bug and release a new package when
