Bug #84476
closed
Backend Scrolling own Extension
0%
Description
Since 8.7.11 no more scrolling in Backend possible for own extension Backend Module.
Updated by Michael Stucki about 6 years ago
- Project changed from 9 to TYPO3 Core
- TYPO3 Version set to 8
Wrong project.
Updated by Stephan Großberndt about 6 years ago
- Status changed from New to Needs Feedback
Please check if thisbis a duplicate of #84264 and that solved your issue
Updated by Stephan Großberndt about 6 years ago
- Related to Bug #84264: Backend not scrollable added
Updated by Uwe Jakobs about 6 years ago
Hi all,
I can confirm this Bug both in 8.7.11 and 8.7.12.
#84264 did not really help.
With me, it occured with the extension "revslider" by Manfred Rutschmann.
Reason is that the iFrame #typo3-contentIframe in typo3\sysext\backend\Resources\Private\Templates\Backend\Main.html (line 17) has added a
scrolling="no"
- before 8.7.11:
<iframe name="list_frame" id="typo3-contentIframe" class="scaffold-content-module-iframe t3js-scaffold-content-module-iframe"></iframe>
- since 8.7.11:
<iframe name="list_frame" id="typo3-contentIframe" scrolling="no" class="scaffold-content-module-iframe t3js-scaffold-content-module-iframe"></iframe>
If you restore it to the old version (or replace "no" with "yes"), everythings runs fine & nice.
I could not find any implication on the general behavour so far.
I did a contribution under [[https://review.typo3.org/#/c/56439/]] and now wait for further information.
Best regards
Uwe
Updated by Maximilian Anton Grimm about 6 years ago
i just added
.tx-myextension {
height:100%;
overflow-y: scroll;
}
and scrolling is working again in all Browsers.
Updated by Riccardo De Contardi almost 6 years ago
- Related to Task #84522: Fix for Backend not scrollable added
Updated by Riccardo De Contardi almost 6 years ago
- Category set to Backend User Interface
Updated by Markus Kappe almost 5 years ago
It works, when the extension author uses the fluid <f:be.container> to render the output.
Updated by Susanne Moog over 4 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Susanne Moog almost 4 years ago
- Status changed from Needs Feedback to Closed
I'm going to close the issue now, extension authors should use the provided API (see previous comments) for rendering templates in backend context. Failing to do so may have side effects as the backend CSS might change at any time as long as the API continues to work.