Project

General

Profile

Actions

Bug #24892

closed

Pagetree cause endless loop in ExtJS events

Added by Steffen Kamper over 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Must have
Category:
-
Target version:
Start date:
2011-01-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Steps to reproduce:

  • Reload the Backend
  • open javascript console
  • execute this snippet
    Ext.util.Observable.prototype.fireEvent =
        Ext.util.Observable.prototype.fireEvent.createInterceptor(function() {
            console.log(arguments);
            return true;
        });
    
  • call page module, watch console output

(issue imported from #M17407)


Files

17407.patch (954 Bytes) 17407.patch Administrator Admin, 2011-01-30 02:05
17407_v2.patch (2.07 KB) 17407_v2.patch Administrator Admin, 2011-02-01 13:13
17407_v3.patch (2.98 KB) 17407_v3.patch Administrator Admin, 2011-02-03 13:17
17407_v5.patch (3.57 KB) 17407_v5.patch Administrator Admin, 2011-02-04 00:04

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #24836: 4.5. Backend is broken in Internet Explorer 6ClosedRupert Germann2011-01-26

Actions
Actions #1

Updated by Eric Auchterberge over 13 years ago

Patch solved the endless loop issue in my installation.

I was looking at all pagetree related issues because pagetree was not loading at all, the strange thing is that only after I executed your snippet in the console, to verify your new issue, pagetree appeared.

To resume, I've applied the patch and both issues (endless loop and in my case no pagetree load) are solved.

Actions #2

Updated by Steffen Kamper over 13 years ago

as Steffen reported problems with first render, i researched it and removed the afterrender listener complete.

Now, everytime if items are added or removed, i add a doLayout call. This is done from the parent container, which is the correct way to do.

Please find attached patch version 2 and test it.

Actions #3

Updated by Eric Auchterberge over 13 years ago

Yep, noticed the first render issue, even after applying first patch.

Tested the second patch on a new install, it fixes the endless looping and issues with first render (even seem to be a bit faster)

Actions #4

Updated by Steffen Kamper about 13 years ago

Committed to trunk and 4_5 (rev 10379/10380)

Actions

Also available in: Atom PDF