Bug #44745
Slider split preview uses only part of the available height
| Status: | New | Start date: | 2013-01-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Workspaces | Spent time: | - | |
| Target version: | 7.5 | |||
| TYPO3 Version: | 4.7 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: |
Description
It's already been mentioned in http://forge.typo3.org/issues/11539#note-5 but in current versions of many browser the slider split preview will only use a small part of the screen in certain cases.
It seems that JS errors/warnings prevent the iframes from using the full height of the browser and they are displayed with only approximately 150px height (as noticed in http://forge.typo3.org/issues/11539#note-11 ).
Tested on Windows Vista the following browsers were tried:
- Chrome: displayed full height of browser
- Firefox, Opera: only 150px
- IE9 : only 150px plus the slider couldn't be dragged
Screenshot: see http://forge.typo3.org/attachments/4799/comparison_view_ff36_mac.png (from issue #11539)
Related issues
History
#1 Updated by Oliver Hader over 2 years ago
- Status changed from New to Needs Feedback
- Target version set to 4.5.23
Do you have a stack trace of the mentioned JavaScript error available. I'm still wondering why a problem inside an IFrame causes the parent frames/documents to have issues as well.
#2 Updated by Hercules Karvasonis about 2 years ago
I am also able to reproduce that on latest TYPO3 4.7.12.
I followed those steps:
- Clicked on the Workspace module
- Generated a preview link
- Viewed the page with that link
- Opened the page from within the backend with the slider view and the height is very small.
In this case if i delete the "ADMCMD_prev" cookie then the page with the slider loads correctly.
Did anyone else find any way to reproduce that or fix it?
#3 Updated by Sven Proffe over 1 year ago
Did anyone else find any way to reproduce that or fix it?
It's reliably reproduceable on TYPO3 6.1.6. Obviously not fixed yet. Could someone set this issue to "Must have"? This error is pretty annoying and quite unexplainable to editors.
BTW: The Live view throws this error:
Fatal error: Call to a member function getSessionData() on a non-object in typo3/sysext/workspaces/Classes/Hook/TypoScriptFrontendControllerHook.php on line 49
Seems to me, that this is responsible for the bug.
Thanks & regards
Sven
#4 Updated by Michael Stucki over 1 year ago
- Category changed from Bugs to Workspaces
#5 Updated by Michael Stucki over 1 year ago
- Project changed from Workspaces & Versioning to Core
- Category changed from Workspaces to Workspaces
#6 Updated by Alexander Opitz over 1 year ago
- Is Regression set to No
@Hercules Karvasonis
your issue sounds more like http://forge.typo3.org/issues/18761
#7 Updated by Thomas Sperling over 1 year ago
I have the same issue. I researched and found out the problem is that backendDomain is not set in the IFrame. So you got in the parent 'document.domain = "xyz.domain.de"' and in the IFrame 'document.domain = ""'.
A similiar problem is maybe related: http://forge.typo3.org/issues/30643
#8 Updated by Alexander Opitz about 1 year ago
- Status changed from Needs Feedback to New
- Target version deleted (
4.5.23)
#9 Updated by Hercules Karvasonis 9 months ago
Alexander,
i tried the fix from issue #18761 and it is not working.
I can still experience the issue as i described it above.
Thanks,
Hercules Karvasonis.
#10 Updated by Mathias Schreiber 6 months ago
- Target version set to 7.5