Actions
Bug #92188
closed
Deferred image processing in the backend is only partly implemented
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-09-03
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
The following issues exist with the current implementation:
1. Image processing is only deferred, when implemented in code¶
Every place in the backend that processes images (inkluding third party code) needs to use
the provided API to pass the images through a processing script
2. Even if the images are already processed, the request goes through PHP and the TYPO3 bootstrap¶
This fact is a waste of resources on every side. Images aren't cached by browsers, thus downloaded on every request,
PHP is triggered with heavy TYPO3 boostrap consuming resources on the server side
3. Target width and height aren't known upfront, causing layout shifts while loading the images¶
Due to the current implementation of just generating a processing URL, the final dimensions of the image are not known
and thus not pssed into the resulting HTML code. This leads to layout shifts once the browser finally fetches the image with its dimensions
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Actions