thx for the PR!

how to reproduce the issue you are fixing? which IE version is affected?

Hi,
I reproduced this error by setting up a basic form with 2 required fields and using IE 11 with enabled compatibility mode (Go to settings -> Compatibility View Settings -> Add the website address, in my scenario is localhost)

Open the page
Click on the first field
Then click on the second field

When focusing out from the first field, the error appears.

This is my validation setup:

$('.login-form').validate({    errorElement: 'span',     errorClass: 'help-block',     focusInvalid: false,     rules: {        UserName: {            required: true        },        Password: {            required: true        }    },    messages: {        UserName: {            required: resources.IngresarUsuario        },        Password: {            required: resources.IngresarPWD        }    },    invalidHandler: function (event, validator) {         $('.alert-danger', $('.login-form')).show();    },    highlight: function(element) {         $(element)            .closest('.form-group').addClass('has-error');     },    success: function (label) {        $(label).closest('.form-group').removeClass('has-error');        $(label).remove();    },    errorPlacement: function (error, element) {        $(error).insertAfter($(element).closest('.input-icon'));    }});

@staabm

how to reproduce the issue you are fixing? which IE version is affected?

hasAttribute is supported as of IE8. And because we still support down to jQuery 1.7.2 which in its own support IE 7, we have to replace all the 4 occurences ofhasAttribute with their equivalent in jQuery using.attr().
That's the main reason why I added thebug label to the linked issue.

We definetly should drop older versions of jQuery in the next major release and stick to versions>v1.10.0,>2.2.0 andv3.0.0 or just support the latest stable version (v3.x.y)

That's the main reason why I added the bug label to the linked issue.

hmm either the linked issue was added after I did the comment or I missed it completely.
thx for the hint.

We definetly should drop older versions of jQuery in the next major release and stick to versions >v1.10.0, >2.2.0 and v3.0.0 or just support the latest stable version (v3.x.y)

big 👍 .

we should gather some information which usefull BC breaks we should target for 2.0.

Hi@lopezcjf,

Sorry for taking so long to review this.

I did some research in order to have a global understanding of this issue and I was wrong suggesting using.attr() to fix this.
I found out thatcontenteditable is supported as ofIE6 and so we can easily replace the check withelement.isContentEditable which returnstrue is the element is editable otherwise it returnsfalse.
This will help us with the case where the element has nocontenteditable attribute but it inherits the editable state from its editable parent (contenteditable = "inherit").

So, can you please update this PR to useisContentEditable property instead.

Hi@lopezcjf,

Just a friendly reminder.

Are you still willing to continue this PR? No worries if you don't have time for it, though.

Thanks!