Bug #85686
closedsvg-tree-wrapper fixed height
0%
Description
The svg-tree-wrapper seems to have a fixed height of 400px, even though the height of the actual SVG inside is updated dynamically. It means on a mac (where scrollbars are hidden) it is not obvious you can scroll.
Would suggest either removing the height attribute, or updating it along with the SVG.
The only related issue I can find is this one: https://forge.typo3.org/issues/77827
Files
Updated by Tymoteusz Motylewski over 6 years ago
Hi
Thanks for the report. 2 questions:
- why are the scroll bars hidden?
- can you attach some screenshots?
Updated by Mike Street over 6 years ago
- File landing.png landing.png added
- File scrolling.png scrolling.png added
If you have an apple mouse or a trackpad connected to OSX, it hides the scrollbars until you start scrolling - this is an intended feature, however, if a box is not obviously scrollable the user can get confused.
Have attached 2 screenshots:
Landing - this is what the page looks like upon landing
Scrolling - this is what it looks like when starting to scroll (note the thin scroll bar on the right)
Updated by Riccardo De Contardi over 6 years ago
- Category set to Backend User Interface
Updated by Benni Mack over 3 years ago
- Related to Bug #77827: TCA SVG tree container is getting too large added
Updated by Benni Mack almost 3 years ago
- Status changed from New to Needs Feedback
Hey Mike,
I guess this is now solved with TYPO3 v11, can you confirm this?
Updated by Riccardo De Contardi about 2 years ago
- File Schermata 2022-09-17 alle 11.18.58.png Schermata 2022-09-17 alle 11.18.58.png added
- Status changed from Needs Feedback to Closed
I confirm that this issue is solved on both 11.5.16 and the latest master (12.0.0-dev);
- I use MACOS X 11.6.8
- On both TYPO3 versions, the scroll for the category tree becomes automatically visible when there are too much items for it, it is not shown just when starting the scroll (see attached screenshot).
I therefore close this issue as solved.
If you think that this is the wrong decision or there is still work to be done, please reopen it or open a new issue with a reference to this one.
Thank you