Bug #58441
closedDisplaced button in workspace preview toolbar
0%
Description
The workspace preview in the TYPO3 frontend shows a toolbar at the top for several workspace related actions.
However, the whole toolbar and its buttons have visual bugs and look displaced if the screen is resized.
- wsPreview_1.png
- wsPreview_2.png
Files
Updated by Oliver Hader over 10 years ago
- Subject changed from Displaces workspace preview buttons to Displaced workspace preview buttons
Updated by Oliver Hader over 10 years ago
- Subject changed from Displaced workspace preview buttons to Displaced button in workspace preview toolbar
Updated by Hercules Karvasonis over 10 years ago
I am not sure also if it is related to this issue or not and to the updates that have happened at the top bar on 6.2, but when i click the List View button on this screen then nothing is shown there and a couple of js errors are thrown.
Updated by Hercules Karvasonis about 10 years ago
- File 58441.diff 58441.diff added
I did some CSS updates for fixing the styling on the displaced buttons.
You can find attached a diff file with those changes.
Thanks,
Hercules.
Updated by Oliver Hader about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Oliver Hader about 9 years ago
- Complexity changed from medium to hard
Updated by Riccardo De Contardi over 8 years ago
This problem is still present on TYPO3 7.6.10 but is absent on 8.3-dev (latest master)
The only problem I see so far in master is that reducing the window size, the label "live" goes under the tabs (see attached screenshot Schermata 2016-07-30 alle 19.36.11.png)
Updated by Riccardo De Contardi over 7 years ago
- File Schermata 2017-04-17 alle 19.13.17.png Schermata 2017-04-17 alle 19.13.17.png added
- Status changed from Accepted to Closed
I close this one, as it has been solved for version 8.7(latest master) - even the problem I've reported on my last comment - see attached screenshot - and it will not be fixed for version 7, as this version enters the "priority bugfix mode".
If you think that this is the wrong decision, then please repoen it or open a new issue with a reference to this one. Thank you.