Bug #61377

Epic #58282: Workspaces Workpackage #2

Story #60008: Visual enhancements

Workspace Preview slider does not scale properly

Added by David Benjamin 11 months ago. Updated 6 months ago.

Status:Accepted Start date:2014-09-05
Priority:Should have Due date:
Assigned To:- % Done:

0%

Category:Workspaces Spent time: -
Target version:7.5
TYPO3 Version:6.2 Is Regression:No
PHP Version:5.3 Sprint Focus:
Complexity:

Description

  1. Select a workspace to preview.
  2. Scale the window, notice the slider does not scale.

I am using Mozilla Firefox Web Browser ESR, Version 24 on openSuSE 13.1.

See the attached screenshot.

WorkspaceError2.jpg - Slider is over the Workspace tab. (103 kB) David Benjamin, 2014-09-05 16:27

WorkspaceError5.jpg (6.9 kB) David Benjamin, 2014-09-22 17:59


Related issues

related to Core - Bug #61374: Workspace Preview unusable due to size Closed 2014-09-05
related to Core - Bug #44745: Slider split preview uses only part of the available height New 2013-01-23

History

#1 Updated by Lorenz Ulrich 11 months ago

In my case the problem is that 'document.domain' in the iFrames is empty (not in the parent frame). This makes the browser fail.

In PreviewController->indexAction the "backendDomain" is evaluated like this:

$this->view->assign('backendDomain', GeneralUtility::getIndpEnv('TYPO3_HOST_ONLY'));

In TypoScriptFrontendControllerHook->hook_eofe it is done like this:

'backendDomain.' => array('value' => $GLOBALS['BE_USER']->getSessionData('workspaces.backend_domain'))

In my case, the backend_domain from the session data is empty. When I change it to

'backendDomain.' => array('value' => \TYPO3\CMS\Core\Utility\GeneralUtility::getIndpEnv('TYPO3_HOST_ONLY'))

it works. I don't understand why in the latter case sessionData is used and in the first case the environment variables.

#2 Updated by Oliver Hader 11 months ago

  • Status changed from New to Accepted
  • Parent task set to #60008

I agree, the visual components look "ugly" and do not respond to changed screen sizes..

#3 Updated by David Benjamin 11 months ago

I applied the patches in from issue #61699. It fixed issue #61374 but not this one.

I have attached a screen shot.

#4 Updated by Mathias Schreiber 6 months ago

  • Target version set to 7.5

Also available in: Atom PDF