Comments on: Dealing with unqualified HREF values (Part 2)

By: pbfranklin.mtech@gmail.com

pbfranklin.mtech@gmail.com — Wed, 19 Dec 2007 14:53:41 +0000

could please any one tell how to get the href value from page in script function in the same page….

By: Julien Royer

Julien Royer — Fri, 19 Oct 2007 08:33:41 +0000

@brothercake: thank you for your answer. I thought the browser would wait for the image to be added to the document tree before making the server request, but you seem to be right.

I don’t understand why browsers don’t offer the possibility to natively qualify an URL.

By: brothercake

brothercake — Thu, 18 Oct 2007 05:17:22 +0000

Yup that’s a pretty neat hack, and in most cases works perfectly well.

My major concern with it is that every time it’s used it makes a server request, which adds to the latency and process overhead of an application that uses it, as well as making it unsuitable for use in abstraction (where you don’t have access to a document object). It will also fail if the href is an empty string (returning an empty string, instead of a reference to the parent folder).

It’s the server request thing that would make me not want to use it; but still, it’s a nice solution :)

By: Julien Royer

Julien Royer — Wed, 17 Oct 2007 11:49:25 +0000

@logic_earth: the src attribute is a complex attribute (a setter/getter couple), which does as far as I know consistently return the qualified URL in the current browsers (FF, IE, Opera, Safari).

By: logic_earth

logic_earth — Wed, 17 Oct 2007 11:02:27 +0000

I don’t understand Julien, how does that snippet make a qualified URI?

By: Julien Royer

Julien Royer — Wed, 17 Oct 2007 08:56:05 +0000

I think there is a much more easier solution:

function qualifyHREF(href) {
  var img = document.createElement("img");
  img.src = url;
  return img.src;
}