On Saturday 22 December 2007, Nicolás Sanguinetti wrote:
> On Dec 21, 2007 9:19 PM, Michael Schuerig <[EMAIL PROTECTED]> wrote:
> > I've run it in Firefox 2.0.0.11 using Prototype 1.6.0.1. The output
> > I get is this
> >
> > [FAIL] should respond to m with: undefined
> > [FAIL] should greet me with: undefined
>
> Yeah, it would have worked if you used 'return this.c.should...'. I
> know it's stupid, it was a quick way out to have it working
> yesterday. I'll commit in a little while the changes which include
> the HTML reporter and stop requiring 'return' in every test, among
> other things
This is one of the things I just don't notice. I was completely
flabbergasted why undefined was returned from a call to apply somewhere
inside js-spec. Of course, I know that JavaScript needs explicit return
statements, but I'm so used to Ruby that I simply don't notice when
they're missing.
I've looked into 0.2 and it still doesn't work, at least for me, on
Firefox 2.0.0.11. I think this line from Context#toElement is just too
clever
var element = new Element("div").insert(new
Element("h3").update(this.name)).insert(new Element("ul")), list =
element.down("ul");
The div is inserted alright, but the nested h3 and ul are not there and
consequently list is undefined.
Michael
--
Michael Schuerig
mailto:[EMAIL PROTECTED]
http://www.schuerig.de/michael/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
