TYPO3 Core

Quoting myself: So we must make each page that is generated by the core and/or any sysext validate to avoid any unintended browser behaviour.

This means: First we have to fix the bugs in our own code, then we might find out which are bugs of the different browsers and how to handle them.

thanks for tracking this down, Joey.
I was able to reproduce the "random" logoff by e.g. opening DB check->Full search or in some modules of the extdeveval extension. "Loaded Extensions" in EM also logged me out. Clicking the "switch compatibility mode" button manually ends the session too.

The suspect In EM is the <select> Module Menu, which neither got a <form> as a container nor an action, but a weird onChange jumpToUrl JS behaviour that could have been easily acchieved with a real form and action, some hidden fields and onChange="submit();" instead.

Since this menu is generated by t3lib_befunc I guess it will be responsible for other BE modules as well.

And depending on the selected function there are quite a few end tags for elements which are not open. (i.e. </fieldset>)

i start cleaning the HTML. But i'm scared by the nested forms problem, it's a general lack of template::form which start normally at the real beginning of the document and can't be closed in inner divs because of the container structure. Mostly this comes from the search form displayed at the end of the page.

Maybe this is one for T3UXW09? I guess validating the HTML output and fixing bad browser behaviour this way can be regarded as a usability improvement.

Since Benni Mack will be in charge as the leader of the developer unit there, maybe he can say something about it. So could you assign this one to him and switch it to "feedback" please?

i contact Benni on skype and stick him to this.

I can confirm this behaviour with the 4.3.0 release. IE8 often switches into compatibiltiy mode that forces immediate user logout. This happens by opening some flexforms or popups. A reproducable example: Try to open the browser popup under "templates" -> "include basic templates".

Therefore it´s impossible to use IE8 for backend purposes this time.

Some more reproducable examples:

1. Ext Manager: select "Check for extension updates", then select "loaded extensions"
2. Klick the Pageicon of any Page in your tree -> select "edit" from the contextmenu
3. DB check: switch from "total pagetree" (and some others) to "Full search"

Some of them don´t happen always, but for sure at the second try.

I recently had to use TYPO3 in IE8 and those "random" logouts make TYPO3 nearly unusable.

Considering the market share of IE this really should be improved quickly!

I also have the problems with the random Loggout with my FE-Sessions...

#21065 (which is a duplicate of this) is already pending in core list and has enough +1s to be committed

Sorry - but this is not a duplicate - it's not even close to being a duplicate, since 11968 is just removing the symptom of being logged out by forcing IE8 into a certain mode.

This one is about getting errors in HTML, CSS and JS fixed, that are the cause for these symptoms, which is something completely different, since it will force people to use more than just Firefox for development instead of ignoring over 50% of the web users and forcing their browser to accept the errors Firefox doesn't care about.

Okay Joey, I removed the relationship again.

For us developers, I admitt that it would be better to see the errors.
But what counts for the users is that their TYPO3 works, and the X-UA-Compatible flag is IMHO (currently) the only possible solution.

as long as this won't be the reason to go on as usual ;-)

Just check the trunk of t3uxw final with IEx to get a rough idea of the catastrophe we are heading for.

Hehe.. I think we all know that there's still a LOT to do to get our T3UXW work in ;-)

BTW: Especially developers of so called "Enteprise" CMSs should take care about MS products, since many of those enterprise clients rely on them.

hello everyone

thx for the info that this was fixed in 4.3

will there be a fix for 4.2?

greetings

Hi Olli,

I think, the problem isn´t fixed, but version 4.3.1 has now a workaround, which seem to help. I never got these logoffs with older versions (4.1x, 4.2.x).
The workaround is also in latest version 4.2.11. It inserts a new meta-tag in backend pages:

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

that´s all.

#21065 has also been committed to 4-2, so the X-UA-Compatible tag is also in 4.2.11

err, what i ment... since there was a link here from the following bugreport by me: 12901

the random sporadic logoffs are gone, thx for that one.

but the 12901 wasnt fixed by that.

I think #21783 isn't related to this