All the equalTo examples use id-selectors, so it doesn't matter where the element is located. Do you have a specific issue this is addressing where the restriction to the form is needed? That would help to come up with unit tests and documentation.

It's a very error prone to use id-selectors in a complex administrative web applications with a lot of forms. Risk to create a collision is too high. I'm prefer to use in a such interfaces a more simple selectors by name in context of form.

I will add a unit tests and a documentation in next commits.

Another reason to apply my patch is to have a same behavior with 'required' method.

ping ;)

Thanks for the test. The change is reasonable, too. I'm wondering how many people currently use the equalTo method with a target outside of the current form. In that case, this change would break their setup. Both 1.10 and 1.11 each have severe bugs that broke existing sites, so I don't want to add to the pile with something that I can see coming.

Unless you have a better idea, I'll keep this open for some more time, until I can make a cut to a 2.0 release with more backwards incompatible changes.

Is there still interest in getting this PR landed?