oliver.hader at typo3.org
Tue Jul 3 10:06:38 CEST 2018
Am 04.10.10 um 10:14 schrieb Jigal van Hemert:
> On 4-10-2010 9:35, Steffen Kamper wrote:
>> what about setting them to deprecated? I think we don't need these for
>> modern websites as there are enough "clean" solutions out using jquery
>> or other js plugins.
> That won't fix the accumulation of .js files for another three years or so.
> Most menus can be done with CSS only, but these dinosaurs seems to be
> still in use and filling up the file system with .js files...
> So, marking them as deprecated is definitely a good idea, but for a
> separate RFC :-)
<strong>Good one</strong> - I'm currently just searching a bit in TYPO3
history... Getting rid of those JS files that mostly contained
duplicated and redundant content based on date/hashes... basically
<i>just</i> boiled down to the following (in an abstract way):
<script>console.log('TYPO3.content:', new Date());</script>
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
More information about the TYPO3-team-core