Description
When navigating within a document the response time for the PageSelect feature takes twice as long as for other features like StepNextPage for example. This shows can be tracked in the Network-Analysis tools in the browser, where it shows two responses. One for the POST-Request, one for the Redirect-Action happening.
Reproduction
Steps to reproduce the behaviour:
- Take a large object for better observation
- Use "Next Page" to go to the next page and inspect response time in browser
- Use "PageSelect" to go again to the next page and inspect response time
- Using PageSelect shows, that it took nearly twice as long to resond.
Expected Behavior
Using PageSelect takes more or less the same time as any other navigation feature. This discussion showcases a possible way to solve this: #1866
Screenshots and Examples
StepPageNext
PageSelect
Environment
- Observed with Kitodo.Presentation 5.x and (upto)
main
Additional Context
The Form-Action is not handled directly by the targeted controller. Instead Typo3 executes the normal plugin chain, renders all elements, creates a response for the POST-Request. After that the POST-Request is handled in the pageSelectAction, the redirect link created and followed. The whole page is basically rendered and shipped twice.
Description
When navigating within a document the response time for the
PageSelectfeature takes twice as long as for other features likeStepNextPagefor example. This shows can be tracked in the Network-Analysis tools in the browser, where it shows two responses. One for the POST-Request, one for the Redirect-Action happening.Reproduction
Steps to reproduce the behaviour:
Expected Behavior
Using PageSelect takes more or less the same time as any other navigation feature. This discussion showcases a possible way to solve this: #1866
Screenshots and Examples
StepPageNext
PageSelect
Environment
mainAdditional Context
The Form-Action is not handled directly by the targeted controller. Instead Typo3 executes the normal plugin chain, renders all elements, creates a response for the POST-Request. After that the POST-Request is handled in the pageSelectAction, the redirect link created and followed. The whole page is basically rendered and shipped twice.