@AMuigai @SGautam_WMF @hueitan @eamedina

Wondering what to do with the loading state if we remove the error state. When we show the loading state, we don't know yet if there is going to be an issue. I see a few solution but I don't know if any of them is good:

1. Show the loading state briefly until the API response arrives then hide everything if there's an error. To avoid the big flash of the loading state we could use cursor: progress to indicate that something is going on.
2. Get rid of the loading state and only show a preview when we know for sure that the preview is valid. The risk here is that users don't wait long enough on target elements to actually see the preview.

For the loading state, I like showing something simple what about the one we are using for the loading state inside gallery.

We want editors/integrators to be able to troubleshoot errors caused by invalid configuration. We'll add specific console.error messages for all the cases we can find.

Is the idea here to use the browser inspect mode to check the console panel? If so, I think it would be helpful for folks who have some technical knowledge though I guess we would still need to add it somewhere on the plugin page, maybe screenshots or FAQ. Shall we also add some helpful tips on error state for folks who won't be using the console panel?

https://github.com/wikimedia/wikipedia-preview/pull/146

The PR is merged.

I tested this by using invalid and unsupported page titles in the storybook.

discussion happening on github

Is there any pending question? From what you are describing in github, it looks like it is working as expected even though the preview is not always helpful.