Funny thing, I never wanted to touch JavaScript, but here we are...
On Oct 22, 2011, at 6:58 AM, Steve Eynon wrote:
> Blimey,
>
> It looks like you worked hard to find that one!
>
> Well done!
>
> Steve.
>
>
>
>
> On 22 October 2011 17:30, Lenny Primak wrote:
>> I found the bug in undersc
Blimey,
It looks like you worked hard to find that one!
Well done!
Steve.
On 22 October 2011 17:30, Lenny Primak wrote:
> I found the bug in underscore.js, and it's a serious one.
> https://issues.apache.org/jira/browse/TAP5-1716
>
> I also submitted a bug for underscore.js itself.
>
> On O
I found the bug in underscore.js, and it's a serious one.
https://issues.apache.org/jira/browse/TAP5-1716
I also submitted a bug for underscore.js itself.
On Oct 22, 2011, at 3:56 AM, Lenny Primak wrote:
> Never mind, the 'old' contains() works correctly.
> This actually seems to be what's wrong
Never mind, the 'old' contains() works correctly.
This actually seems to be what's wrong with the new code,
the scripts that should not be reloaded (datepicker.js) are reloaded when zone
is refreshed.
On Oct 22, 2011, at 3:53 AM, Lenny Primak wrote:
> Digging there even further,
> it seems that
Digging there even further,
it seems that the old addScripts() had a bug that
Tapestry.ScriptManager.contains(document.scripts, "src", ...)
would silently throw the exception every time, and the scripts would never get
reloaded, which masked the problem.
With this code reworked, scripts actually
Digging further into this, the problem is actually triggered by the GWT
JavaScript that's on the same page.
I can't reproduce this unless I have a GWT component on that page, any GWT
component.
I believe something was broken with
http://svn.apache.org/viewvc?view=revision&revision=1186564
It se
Just upgraded to beta-26, and started getting JavaScript errors when
submitting an AJAX form.
search object has a Date (hence the DateField bean)
I get the following errors starting sometime after beta-21 (it worked perfectly
in beta-21)
