Bug #22823
closedHighlighting in typo3pageModule.js is disabled for each version of IE
0%
Description
The comment states that Highlighting doesn't work for IE and therefor all elements should be set to visible instead.
Again this is just a workaround, this time for a bug in ExtJS that uses the "mouseenter" and "mouseleave" events in a wrong way.
The problem now is to find an appropriate fix for this ExtJS bug or replace it with a hand made non ExtJS script.
The Code Cleanup Team will be working on it.
So please discuss this issue there.
When assigning these events to a div container, they only will be triggered when the mouse hovers over a text, a border or another "real" content inside the div, but not when it's hovering any kind of background (except "real" background images).
The bug is not caused by IE since a simple <div onmouseenter="alert(Test);">Whatever</div> works as expected in each version of IE regardless of any "real" content.
The funny thing is, that "mouseenter" actually is used by IE only and the ExtJS implementation is just a hack to make it work in other browsers as well. In this case it breaks the functionality which is originally working in IE.
(issue imported from #M14633)
Files
Updated by Jo Hasenau over 14 years ago
The attached patch solves the problem described above AND solves another bug with editing icons in IE8 being non clickable.
The reason for this misbehaviour was invalid HTML code, since the page module had a nested form tag, due to a missing parameter while calling getSearchBox wihtin the page module form.
Updated by Jo Hasenau over 14 years ago
layout.patch contains the modified JS file as well
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
AS #8075 is fixed, is this issue also fixed?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No response in over 3 month so closing this issue.
If you think this issue should be reopened, then write to the bugs mailing list.