Suggestion #7617
Inline javascripts removal & move everything to bottom
| Status: | Accepted | Start date: | 2010-05-04 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | JS | Spent time: | - | |
| Target version: | - | |||
| Votes: | 0 |
Description
TYPO3's one of biggest issues – inline javascripts. They are everywhere – in login form, in backend. We should move them to separate script files, as inline javascript – more content to load each time.
And – we should move all scripts to bottom of content – before closing body tag, as it would reduce page rendering time.
History
Updated by Jo Hasenau about 3 years ago
- Category set to JS
- Status changed from New to Accepted
- Priority changed from Must have to Could have
Currently the plan is to take care of it in phase 2 of the project.
The major goal is to improve the code quality, while leaving the structures more or less untouched. After all this will lead to X-browser valid HTML, JS and CSS code to make sure the rest of the bugs is caused by the browsers and not TYPO3.
In phase 2 we can take care of these bugs then and start to change the structures as well, so we will get a better performance and other improvements as a nice side effect.
This is why I set this to "could have", which might be changed in phase 2.
Updated by Daniel Unterberger almost 2 years ago
Kristaps Karlsons wrote:
TYPO3's one of biggest issues – inline javascripts. They are everywhere – in login form, in backend. We should move them to separate script files, as inline javascript – more content to load each time.
And – we should move all scripts to bottom of content – before closing
bodytag, as it would reduce page rendering time.
for a temporary solution, one can use php-tidy extension to move the inline styles at least into header and convert them into classes automatically. then use this autogenerated code to review all places of inlinecode and cleanup the code.