Core

Does that also happen on current "master" (6.2 development)? I ask because we added the "X-UA compatibility" flag there to make IE know that the backend is "IE10 compatible" (used to be IE9). Maybe this affects this particular scenario?

Markus Klein wrote:

So the login basically works right?

I tested this on 4.5, 4.7 and 6.1 now and everywhere the same behaviour.
But there's a link below saying "Ignore ...".

This allows to login as normal.

Right, but some of our editors are confused. They still call...

Ernesto Baschny wrote:

Does that also happen on current "master" (6.2 development)? I ask because we added the "X-UA compatibility" flag there to make IE know that the backend is "IE10 compatible" (used to be IE9). Maybe this affects this particular scenario?

Ernesto that was also what I thought so I directly tried my dev-system at work. But this also happens on 6.2:(

relevant part is in typo3/sysext/t3skin/Resources/Public/JavaScript/login.js:

checkCookieSupport: function() {
        Ext.util.Cookies.set('typo3-login-cookiecheck', true);
        cookieEnabled = Ext.util.Cookies.get('typo3-login-cookiecheck');

if (!cookieEnabled) {
            TYPO3BackendLogin.showCookieWarning()
        }

Ext.util.Cookies.clear('typo3-login-cookiecheck');
    },

Could there be a reason why IE11 does not accept this cookie? Wrong cookie-path or so?

I just found out that with a "normal" browser the user/password-fields would show again. But with IE11 on the error-page they are gone for me. So maybe there is some HTML-error preventing the cookie-check from running at all and/or the boxes from being hidden using CSS.

ah no, the fields are hidden by showCookieWarning() - hmm ...

Patch set 1 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25869

Patch set 1 for branch TYPO3_4-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25870

Patch set 1 for branch TYPO3_4-5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25871

Patch set 2 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25869

in typo3/sysext/t3skin/Resources/Public/JavaScript/login.js in line 166 schould be, for ex.:

Ext.util.Cookies.set('typo3-login-cookiecheck', true, time () + 60000);

Not resolved, I still have this problem in TYPO3 6.1.7 and IE11.

Was merged to 6.1 right after release of current 6.1.7 :-(

Review for 6.1-tree: https://review.typo3.org/25868
Please grab the fix from there and try it out.

I checked, I had already patched it, so unfortunately something's still wrong.

Did you clear cookies and/or maybe completely closed IE11 after patching? Using the F12-developertool from IE I was able during debugging to see that two cookies actually existed. With the patch the same one is set and unset in both cases. But once something went wrong (without the patch) the problematic cookie is there and won't go away itself unfortunately.

Yes, silly me. Cleared Cookies again and no more problems so far.