How to remove the "Loading..." indicator from my taskpane manifest based plugin #5349
Comments
microsoft-github-policy-service
bot
added
the
Needs: triage 🔍
exextoc
added
Area: Outlook
|
Hi @flurin-conradin, If you're using Office.onReady() in your code, ensure that all initialization code that interacts with the Office API is placed within this function. This ensures that the API is fully loaded before your code executes, which can prevent the "Loading..." indicator from persisting. If your add-in performs asynchronous operations during initialization (e.g., fetching data or loading resources), ensure that these operations are completed before indicating that the add-in is ready. Delays in these operations can cause the loading indicator to remain visible. Kindly try the aforementioned resolutions and get back to us in case any issues, thank you. |
patilganesh-msft
added
Needs: author feedback
|
Hello @patilganesh-msft Thank you very much for taking your time. The issue persists. I have stripped down my plugin to the bare minimum. There are two observations which might be of importance:
Thanks in advance for looking into this. <!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<script type="text/javascript" src="https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js"></script>
<title>Email Automation Web Add-in</title>
<script>
Office.onReady(function (info) {
console.log("Office is ready", info);
});
window.onload = function () {
console.log('Page has loaded');
};
</script>
</head>
<body>
<div id="root"></div>
<div>Hello!</div>
</body>
</html> |
microsoft-github-policy-service
bot
added
Needs: attention 👋
I have developed an Outlook addin based on the manifest.xml using office-js. Everything works as expected, but the loading indicator does not disappear, as shown in the picture below
I am running Office.onReady(...) in my React code. Is there anything I could do there to remove it?
Note that this is a deployed addin. I have seen post about similar issues with sideloaded addins.
The text was updated successfully, but these errors were encountered: