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
Describe the bug
If the full screen (Office web) is to be called up during a document search via the preview, the screen twitches briefly but nothing happens.
To Reproduce
Detailed steps to reproduce the behavior:
Add the search result webpart to a page.
(Optional) Add a query to filter for documents (like .pptx)
Select the cards layout
Publish the page.
Open the preview of a search result.
Try to open the full screen
Error: The full screen is not opened
Expected behavior
The full screen (Office Web) shoulde be opend.
Screenshots
Desktop):
Browser MS-Edge (131.0.2903.70)
Additional context
I have seen in the console that an error is displayed by the graph when opening the preview.
In the network tab, the graph endpoint (https://graph.microsoft.com/beta/print/services) returns a 403. I have already tried to add authorisations via the config (and builded it locally) and release them in the Admin Center, but unfortunately the error cannot be resolved.
The text was updated successfully, but these errors were encountered:
I can repro but not sure how to fix it as the preview control is controlled by Microsoft and not sure what events are sent. If someone can figure out a fix we can implement it.
Version used
Ex: 4.14
Describe the bug
If the full screen (Office web) is to be called up during a document search via the preview, the screen twitches briefly but nothing happens.
To Reproduce
Detailed steps to reproduce the behavior:
Expected behavior
The full screen (Office Web) shoulde be opend.
Screenshots
Desktop):
Additional context
I have seen in the console that an error is displayed by the graph when opening the preview.
In the network tab, the graph endpoint (https://graph.microsoft.com/beta/print/services) returns a 403. I have already tried to add authorisations via the config (and builded it locally) and release them in the Admin Center, but unfortunately the error cannot be resolved.
The text was updated successfully, but these errors were encountered: