fat
Normalize handler signature (and test fire)
I made changes discussed in #102 and #80. I used a base Event object and added .type. Doing it that way sets .isBean to true and some non-applicable properties to undefined.
Buster does not work on my PC because it's XP probably. I could not run any Buster tests but I reworked the existing fire() ones based on my changes. I made tests/fire-demo.html to inspect the args for now.
Does .isNative refer to the element, the type, or the element/type combination?
this looks great. I couldn't get buster running either and started to get annoyed by it. It would be good to have this run thru the test suite before moving forward
Thanks @ded I agree about the tests. Let's hope at least @rvagg can run them.
The whole buster-server setup is garbage and doesn't work, you'll have to run the static test page in the various browsers manually. See test.html, tho I haven't run it for ages and last time I checked Buster had problems with Node 1.0 (hence bustermove but that's for server-side). All it needs from Buster is the static assets for frontend testing.
If you have no luck getting this going then let me know here and I'll see what I can do. If need be we'll have to switch out the test framework with something else that's kept up-to-date.
@rvagg that doesn't work either.... mainly because i think buster changed. have a go at a fresh bean setup and you'll notice buster is undefined because buster/resources/buster-test.js does not exist (yes this is after npm install). Likely because bean relies on an outdated version of buster that used to have the file. the package file says ~0.6.2 — but we may need an earlier version