Skip to main content

I was having this issue and it alsowas effecting only seemed to effect the Windows 10, and Infopath 2013 users.

After some examination I found that we had the page set. to:

<meta http-equiv="X-UA-Compatible" content="IE=10" />

it was thenThen I changed this to following:

<meta http-equiv="X-UA-Compatible" content="IE=edge,IE=11,IE=10" />

Tested goodAnd it is working fine.

Hope this helps.

I was having this issue and it also only seemed to effect the Windows 10, Infopath 2013 users.

After some examination we had the page set.

<meta http-equiv="X-UA-Compatible" content="IE=10" />

it was then changed to

<meta http-equiv="X-UA-Compatible" content="IE=edge,IE=11,IE=10" />

Tested good.

Hope this helps

I was having this issue and it was effecting only the Windows 10 and Infopath 2013 users.

After some examination I found that we had the page set to:

<meta http-equiv="X-UA-Compatible" content="IE=10" />

Then I changed this to following:

<meta http-equiv="X-UA-Compatible" content="IE=edge,IE=11,IE=10" />

And it is working fine.

Hope this helps.

Source Link

I was having this issue and it also only seemed to effect the Windows 10, Infopath 2013 users.

After some examination we had the page set.

<meta http-equiv="X-UA-Compatible" content="IE=10" />

it was then changed to

<meta http-equiv="X-UA-Compatible" content="IE=edge,IE=11,IE=10" />

Tested good.

Hope this helps