Version support and iframe refactoring

[juliushaertl]

Fixes #3102
Fixes #3011

Best to be reviewed as without whitespaces

Requires nextcloud/server#40184 for a smooth restore

Sorry I went a bit nuts on refactoring bits in the document controller, so this is a larger changeset, but the relevant changes in summary:

• Introduce a token endpoint to generate a wopi token
• Rework the viewer vue component to request the token from the new endpoint and directly load Collabora in an iframe instead of loading an intermediate page (DocumentController::index) which used to generate the token and load another iframe within
• Remove transition in vue component to avoid flickering
• Move missing post message logic into vue component (as the existing implementation from document.js is no longer used now in the viewer)
• Add cypress tests for important integration parts where the post message handling is happening
• Simplify and merge common logic to get a the file and share for token generation
• With that we can now also load versions through the token endpoint which enables us to make use of the version preview and side by side comparison with 27.1

Summary

• Refactor iframe loading for viewer to only load one instead of two nested iframes
• Generate a token before through an API call
• Implement support for version preview and comparison with viewer
• Remove micro transition for animating the fade in as it caused more troubles then it helped

TODO

• Double check all cases for iframe loading
• Document follow ups to see where we still need to replace the double iframe
  • Public single file shares
  • Direct editing
  • Federated editing
• Cleanup post message handling
• Tests
• Follow up issue for text to handle restore gracefully

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Documentation (manuals or wiki) has been updated or is not required

[cypress]

Passing run #586 ↗︎

0

27

5

0

0

Details:

Version support and iframe refactoring
Project: Richdocuments	Commit: e34a607082
Status: Passed	Duration: 03:02 💡
Started: Sep 8, 2023 9:23 PM	Ended: Sep 8, 2023 9:26 PM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[juliushaertl]

Quick profile of what we save between old and new appraoch

From Viewer loading to actual collabora frame being loaded

Old

Full additional page load with core javascript initialization, times hard to measure reliably but in the profile ~4s

New

Only one API call ~80ms

[juliushaertl]

/backport to stable27

[max-nextcloud]

Just had a closer look at the mixins. They look good except for one catch that i think is too broad.

[juliushaertl]

/backport to stable27

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport