On Thu, Jan 29, 2009 at 9:36 AM, T <a_j...@bellsouth.net> wrote: > > On Jan 28, 10:27 pm, Ricardo Tomasi <ricardob...@gmail.com> wrote: >> Possible it is, but it's a very very heavy burden on the user, >> completely inneficient and unreliable. You'd have to load the URL in >> an iframe and wait for the 'onload' call, if it's not called after a >> certain time you consider the link dead (but it may just be slow at >> the time). No event is fired for an error or loading not complete. >> >> Why would you want to have broken links in your page anyway? >> >> On Jan 28, 7:33 pm, T <a_j...@bellsouth.net> wrote: >> >> >> >> > Hi, >> > I'm new to jquery and javascript in general, so this may not be >> > possible: >> >> > I want to colorize broken links: that is, colorize anchor elements >> > containing hrefs that don't resolve (either missing remote file or >> > missing anchor in remote file). >> >> > Is that possible? >> > thanks, >> > --Tim- Hide quoted text - >> >> - Show quoted text - > > hi, Well, it's not that I want broken links. I run a document > production system that sometimes can produce broken links. What I was > thinking of was using jquery on my build reports page so writers could > easily see their broken links. This would be for development only > (build reports). Maybe it's a bad idea--I get what you're saying about > the load. I thought a call to the href might return 404 or some > 'failed' signal. > > I think you're saying I'm thinking the wrong way about how to address > the problem of broken links. > thanks, > --Tim >
I think what you describe makes perfect sense. Yes, it'd be expensive, but if it's only for building these reports, I don't think it'd be such a bad thing. The .ajax method allows one to set an "error" callback. The 1st param passed to that callback will be the XMLHttpRequest object, and its "status" member should be the numeric response code.
