The "slider" workspace PreviewController has an odd functionality
that can force the backend user into a different workspace when
reloading a given preview using the "previewWS" GET parameter. This
leads to inconsistent UI.
Suppose the following scenario:
* Have two workspaces, one having an additional custom stage.
* Have a live page with a content element.
* Go to workspace 1, change the content element.
* Use the BE workspace module list and click the "eye" to
preview the change of the element. Leave that tab open.
* Go to workspace 2, change the content element differently.
* Reload the still open tab.
* Call the BE workspace module again.
Result:
* The reloaded preview still shows the changes from workspace 1.
* The "next" stage from workspace 2 is used in the preview, even
though content changes from workspace 1 are renedered.
* The BE workspace module "magically" switches to workspace 1
when called again.
* The BE page tree is still workspace 2, and the toolbar workspace
selector still shows workspace 2, too. This only switches to
workspace 1 when the BE is reloaded.
To overcome this weird behavior, we fully remove the 'previewWS'
GET argument: The PreviewController no longer forces a BE user
into some workspace to avoid an inconsistent BE afterwards. When
reloading an open preview tab, the preview now simply uses the
current selected workspace of the backend user, and no longer tries
to show content from a different workspace a BE user may have switched
away from meanwhile.
Note the links from the PreviewController can not be "shared" by
sending them to a different user: The PreviewController is a BE
module controller and as such bound to the browser session. Sharing
workspace previews can only be done using the "Generate Page Preview
Links" functionality. Thus, changing the PreviewController arguments
by leaving out 'previewWS' only impacts the given local browser
session and user.