I don't want to bog the list down with my javascript naivete, but the full
fix to dojo/on.js is something like this:
if (type.call && !(((typeof type) === "string") || (type instanceof
String))){...
On Wednesday, November 28, 2012 9:15:11 PM UTC-8, Brian Nelson wrote:
>
> ok. I've had
I sent a note to the dojo list, so they're aware of the situation.
Meanwhile it's an easy enough work-around to avoid the problem.
-Patrick
On Saturday, December 29, 2012 5:51:32 PM UTC-8, David Nolen wrote:
>
> Yes this is known problem w/ ClojureScript that could be solved if/when we
> get p
Yes this is known problem w/ ClojureScript that could be solved if/when we
get proper Keywords/Symbol types.
David
On Sat, Dec 29, 2012 at 8:46 PM, Patrick Logan wrote:
> From what I can tell, dojo is testing an argument to see whether it has a
> method named "call". dojo seems to be assuming t
>From what I can tell, dojo is testing an argument to see whether it has a
method named "call". dojo seems to be assuming that if such a method
exists, then the argument will not be a string.
Then clojurescript seems to be assigning a function named "call" to the
String prototype. And so these
ok. I've had some time to look into this now and have figured out a few
things.
1. This is not due to calling the DGrid constructor from clojurescript. It
occurs even when I call the DGrid constructor from straight javascript
code. So it doesn't have to do with the clojurescript code calling th
Hi,
I'm brand new to ClojureScript and have been trying to get myself
familiarized with it's javascript interop capabilities by implementing
the Dojo toolkit tutorials. I've successfully implemented several of
the tutorials, but now I've run into something that I can't figure out
and am looking fo
