-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTMLView failing to update (occasionally) #520
Comments
And another example today @EduardMe. Quite a few times I refreshed the Dashboard, but it insisted on not updating, and instead kept the view from the day before. View from left to right is
I'm raising the priority on this, as it seems to be happening increasingly frequently. Restarting NP clears the problem, but not just closing the HTMLWindow. |
@ksanderer is finding this as well. I've asked him to post the details he's collected. |
In the Review plugin folder, I use CloudKit as a sync engine |
Interesting, thanks for sharing. Does it re-render when you click again on update or it stays no matter how often you click? Maybe it completely refuses to reload it at some point. |
It doesn't reload no matter many times I clicked “Refresh” |
@EduardMe I am seeing this a lot and it's very frustrating. Can you please have a look at how we can fix it? |
Fixed and uploading a beta, please confirm once it's available to close this. |
A few times now I've had an existing HTMLView window failing to update, but without any errors in the np-out or np-error logs.
More detail: I've had either Dashboard or Project List window open. I've hit update on the window, and all my usual debug logging shows the expected work, up to and including the usual messages about finding the existing window and calling
await HTMLView.showWindowWithOptions()
. This call seems to return a valid object, as I can read the.customID
and.id
from it.The copy of the HTML that I additionally persist to disk is fine.
But the HTMLView does not update at all, instead just stays the same.
This feels related to the as-yet-unidentified-cause of the missing requiredFiles file that occasionally drops .css files. (Reported in Occasional loss of a Required File)
The text was updated successfully, but these errors were encountered: