larry.karnowski (at gmail)

A Blue Ridge user reported an issue when using Prototype's "Element.down()" method. http://github.com/relevance/blue-ridge/issues#issue/6

I've added a failing "...

We're getting complaints of this from Blue Ridge users:
http://github.com/relevance/blue-ridge/issues#issue/3

Thatcher, now that I can run the jQuery 1.3.1 compatibility test suite from my env.js working directory, I'm starting to refactor the DOM a bit to tackle that n...

Thatcher, sorry for the lack of communication, because I've started working on jQuery 1.2.6 and 1.3.1 compatibility test suites too. My fork (http://github.com/...

Note, we're using this same "return a warning function" technique through out the DOM. I'm thinking of extracting my "fix" into a function that we can reuse for...

I've added a Prototype compatibility test and a patch for this on my GitHub fork. Here are the commits:

Prototype compat test: http://github.com/Lawjoskar/env-...

Prototype sets several of its own properties on the Event object (polluting the namespace) and cannot do so because every time you call the window.Event getter,...

Chris, so after rethinking this, I realize that "compatability" is too broad a word. I'm not asking for 100% compatibility, just that we can do the following:

• ...

I've added a Prototype compatibility test and a patch for this on my GitHub fork. Here are the commits:

Prototype compat test: http://github.com/Lawjoskar/env-...

Prototype's $$("class") method, which is akin to jQuery's $(".class") method, is failing because it's traversing the DOM and expecting each node to have a defin...