You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a problem with Collabora CODE 25.04.2 under Nextcloud 31.0.5.
The last update of Collabora broke something related to WASM support. I had this option turned on because Collabora sets COEP, COOP and CORP headers on this mode.
Now, I had to turn it off because when a document opens it renders the initial view on white and you can't see the document content. When you scroll the content you can see the rest, but the initial content remains invisible.
[Example: I want to do X, but because of PROBLEM, it takes 5 extra steps instead of 1.]
Describe the solution you'd like
I'd like to be able to configure Collabora to set COEP, COOP and CORP header, without WASM support turned on.
I need these three headers:
Is your feature request related to a problem?
I'm having a problem with Collabora CODE 25.04.2 under Nextcloud 31.0.5.
The last update of Collabora broke something related to WASM support. I had this option turned on because Collabora sets COEP, COOP and CORP headers on this mode.
Now, I had to turn it off because when a document opens it renders the initial view on white and you can't see the document content. When you scroll the content you can see the rest, but the initial content remains invisible.
[Example: I want to do X, but because of PROBLEM, it takes 5 extra steps instead of 1.]
Describe the solution you'd like
I'd like to be able to configure Collabora to set COEP, COOP and CORP header, without WASM support turned on.
I need these three headers:
cross-origin-embedder-policy require-corp
cross-origin-opener-policy same-origin
cross-origin-resource-policy cross-origin
I observed that Nextcloud works fine with Collabora when it sets these header.
[Example: When I press on X, I think Y should happen. In other software, this exists under the "Help" tab.]
Describe alternatives you've considered
An alternative would be to handle this on the proxy, so these headers would be added at the proxy stage.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: