Project

General

Profile

Actions

Bug #32357

closed

Optimize loading behaviour of modules

Added by Kay Strobach almost 13 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
-
Target version:
Start date:
2011-12-07
Due date:
% Done:

0%

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

Description

please take a look into t3-trunk/typo3/js/modulemenu.js

There you have a function called loadModuleComponents.

This function basicly does the following:

1. check wether there are navigation components
2. if yes show them
3. load module

So far so good, but the following happens due to the behaviour of the navigation components:

1. check wether there are navigation components
2. if yes show them
3. load module
4. after finishing navigation component load the contentArea is refreshed

So we have two loadings of the content area :(((

Solution:
- set contentArea to about:blank (or an extjs panel with always the same content (please select an element from the tree)
- change function, so that the loading only happens, if there is no navigation component ;)

<<<snipp
    TYPO3.Backend.NavigationIframe.getEl().parent().setStyle('overflow', 'hidden');
    } else {
        TYPO3.Backend.NavigationContainer.hide();
        TYPO3.Backend.NavigationDummy.show();
        --> do reload here only
        --> this.openInContentFrame(record.originalLink, params);
    }
    --> no reload here!
snap>>>

Regards
Kay

PS: Hopefully the declaration as bug is correct, could be also a feature (while i like to see that backported), or a task


Files

2013-10-17_10-41-58.png (145 KB) 2013-10-17_10-41-58.png Kay Strobach, 2013-10-17 10:44
Actions #1

Updated by Philipp Gampe about 11 years ago

  • Status changed from New to Needs Feedback
  • Priority changed from Must have to Could have
  • Is Regression set to No

Can we close this or do you still want to work on this?

Actions #2

Updated by Kay Strobach about 11 years ago

i have not worked on this, but it is still valid, anyway i think you can close it, as i think for 6.3 there will be a different solution ...

Actions #3

Updated by Kay Strobach about 11 years ago

message was in false issue - sry ...

Actions #4

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to New
  • Target version set to 7.0
Actions #5

Updated by Mathias Schreiber almost 10 years ago

  • Target version changed from 7.0 to 7.1 (Cleanup)
Actions #6

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from New to Closed

closed due to reporter request

Actions

Also available in: Atom PDF