SharePoint Online PDF Viewer changed and performs very slowly now

Anonymous
2024-04-11T19:26:20+00:00

Hello,

Our users noticed a change when viewing PDFs in their SharePoint Online document library. Occurred Monday 4/8/24.

They have it set up where when you click on the document from the library, it brings it up with the SharePoint Online PDF Viewer, it does not open in a new tab, and that's the way we prefer. With the viewer, you can click on the info button to bring up the info pane on the right, and you can edit your metadata from there.

They noticed several things.

-The background is now black, like in a dark mode, thats what initially tipped them off that something has changed.

-The info button is no longer available, it is now buried in the ... menu on the top left.

-It is now EXTERMELY slow to load. When they click on the next arrow to view the next PDF, it is very slow to load and also the info pane is very slow to load.

-When they filter or sort the library, and then start viewing the PDFs, it does not bring them up in the same order as the filter/sort. It's completely different.

I as the IT admin, have tried many things to improve performance, here's some notes.

-Not everyone has this new viewer experience. The older experience has a white background, and also the info button. See screenshots to see the difference.

-I am able to reproduce the slowness on other test pcs, though there are a few that seem to load fine.

-I have cleared browser cache, cookies

-Tried with different user accounts

-Tried with private browsers, and tried with Edge Firefox, and Chrome.

-Tried using a hotspot to be on a different network

I have opened up a ticket to Microsoft, but no response yet. I have also not seen any announcement of this change.

Has anyone else noticed this? Any workarounds or suggestions? Any way to roll back to the old viewer? (wishful thinking). I'm wondering if laptop specs are factoring in, which would surprise me because it's basically just web browsing here.

Thanks!
nick

Microsoft 365 and Office | SharePoint | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

93 answers

Sort by: Newest
  1. Anonymous
    2024-05-31T04:24:37+00:00

    We implemented a code fix that should address this problem. The solution will reach all users by June 4th, let us know if you still have that issue after that.

    Best regards,

    Emanuele

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-30T20:30:58+00:00

    For anyone else who finds this, after a few weeks I have been informed by tier 2 Microsoft Support that there is no support available from Microsoft Development. Instead, they pointed me to the feedback portal and said that is the best course of action if Microsoft Development releases anything broken is to leave a message there. There is no guarantee that it will be addressed or read. There will be no information given or follow up for this issue according to Microsoft Support. My ticket was closed.

    Here is the link

    Ideas · Community (microsoft.com)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-05-29T21:44:02+00:00

    Ok, thank you, Carrie. I am assuming you have a support ticket open, because we might need more information to understand the issue.

    Best regards,

    Emanuele

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-05-24T11:39:17+00:00

    Yes, that is correct. The arrows remain absent. I have to close the viewer to move to the next file. I also work w/ many files that look very much alike, so it's hard for me to tell where I left off. I'm now deleting the file and waiting for the refresh as a work around instead of being able to just click the "next" arrow to move on.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-05-24T04:14:02+00:00

    I am having the same problem. The only work around I have found, is to use Edge instead of Chrome.

    Was this answer helpful?

    0 comments No comments