Cool. Can we get this unit tested somehow?

I think we already have some tests for contenteditable elements. One thing I can suggest in order to avoid regressions regarding IE, is for us to apply for a Saucelabs/BrowserStack open source access to use it for testing the plugin in supported IE versions and also on Safari (if it's allowed in the free plan).

Oh I see. Not sure it’s worthwhile for IE.

In case you are condfident with the patch please go ahead and merge it.
If not we can wait for som of the reporters to confirm the fix.

Thank you

It's best to wait for feedback from the reporters. I will provided the build file for them and link to it in#2211.

judging from the code change this seems to do the trick. since i get the package via npm i have no clue how to test the change directly in our project...?

see#2211 (comment) on how to get the fixed version

see#2211 (comment) on how to get the fixed version

this just links to the fixed file. npm would overwrite this during next build

Based on the feedback from the comunity, I am going to merge this.

@staabm could you please release this fix in a minor version (as we also have some new validation rules added)?

You can find the changelog here:https://gist.github.com/Arkni/fc52dc8e4f5ca1ccc7ea1198b0b659a3#file-jquery-validation-changelog-1-19-0-md

Thanks :)

just published 1.19.0 with a fix for this issue.

sorry the any inconvenience this bug has caused for you guys.