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
When a IIIF manifest fails to load in Mirador after typing the URL into the Add New Object box and pressing Load, nothing happens, and it is not immediately clear where the problem lies. For instance, in a workshop, I saw manifests fail to load because of a mistyped URL and because the server was not responding. In each case, the user initially thought the problem was with the app, not the manifest. It would be nice if the app could return an appropriate error message so the user would know it was responding.
(I realize this is a Mirador issue, and I'm not sure whether there's any way to monitor Mirador's request and response. But it was definitely affecting how people used TEI Web Editor, so I thought it was worth mentioning.)
The text was updated successfully, but these errors were encountered:
Great. That's a good issue. Another reason manifests could be failing is
that the manifest needs to be "https", if it is not "https" it won't work
on an "https" site.
But I think we definitely need some user feedback, which shouldn't be too
hard.
I'll look into it.
On Wed, Mar 28, 2018 at 10:18 PM, Paul Broyles ***@***.***> wrote:
When a IIIF manifest fails to load in Mirador after typing the URL into
the Add New Object box and pressing Load, nothing happens, and it is not
immediately clear where the problem lies. For instance, in a workshop, I
saw manifests fail to load because of a mistyped URL and because the server
was not responding. In each case, the user initially thought the problem
was with the app, not the manifest. It would be nice if the app could
return an appropriate error message so the user would know it was
responding.
(I realize this is a Mirador issue, and I'm not sure whether there's any
way to monitor Mirador's request and response. But it was definitely
affecting how people used TEI Web Editor, so I thought it was worth
mentioning.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#22>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ABF_PWivW3A1g2I5Zys81uQpxm2dkABKks5tjERygaJpZM4S_o-e>
.
--
Dr. Jeffrey C. Witt
Philosophy Department
Loyola University Maryland
4501 N. Charles St.
Baltimore, MD 21210
www.jeffreycwitt.com
When a IIIF manifest fails to load in Mirador after typing the URL into the Add New Object box and pressing Load, nothing happens, and it is not immediately clear where the problem lies. For instance, in a workshop, I saw manifests fail to load because of a mistyped URL and because the server was not responding. In each case, the user initially thought the problem was with the app, not the manifest. It would be nice if the app could return an appropriate error message so the user would know it was responding.
(I realize this is a Mirador issue, and I'm not sure whether there's any way to monitor Mirador's request and response. But it was definitely affecting how people used TEI Web Editor, so I thought it was worth mentioning.)
The text was updated successfully, but these errors were encountered: