<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
This has irked me lately...<br>
<ul>
<li> <a> uses <i>href</i> (outbound)
</li>
<li> <link> uses <i>href</i> (inbound and outbound) </li>
<li> <img> uses <i>src</i> (inbound)
</li>
<li> <iframe> uses <i>src</i> (inbound)
</li>
<li> <script> uses <i>src</i> (inbound)</li>
<li> <embed> uses <i>src</i> (inbound)
</li>
<li> <object> uses <i>data</i> (inbound)
</li>
<li> <applet> uses <i>code</i> (inbound)
</li>
<li> css @import (inbound) </li>
<li>I'm sure I missed some more that should be listed here too.<br>
</li>
</ul>
It seems like in all cases these are simply a URI, and whether it
takes you to some place or if it loads in something is purely
contextual.<br>
So why not spec all those to simply be synonyms for href (which is
used both for inbound and outbound).<br>
<br>
I assume that pretty much all browsers do treat these as pretty much
the same anyway or? (i mean code/parsing wise)<br>
None of the above supports both inbound and outbound at the same
time, they are either/or instead, or context dependent.<br>
So if href src data and code and @import all mostly overlap their
implementations, why not spec them to be synonyms and point to the
href spec?<br>
Eventually the synonyms will die out and href and src may just end
up as a visual hint to the author about which direction something
goes.<br>
<br>
The alternative is to go through all those and ensure that href is
always outbound and src is always inbound everywhere in the spec and
that data and code and @import is replaced by src.<br>
<br>
I could care less which is the best solution of these two
alternatives.<br>
A. Everything is a synonym for href, and tag or context determines
inbound/outbound.<br>
or<br>
B. Everything is a synonym for href or src, and href determines
outbound and src determines inbound.<br>
<br>
How does the browsers currently handle this internally? And would
solution A or B require the least changes?<br>
<br>
When using view as source (at least in Firefox and Chrome) and then
clicking on say a src uri will treat it as if it was href, so here
src and href are synonymous and context determines behavior. Though
one could argue the document source has been transformed into a new
document for display.<br>
<br>
<pre class="moz-signature" cols="72">--
Roger "Rescator" Hågensen.
Freelancer - <a class="moz-txt-link-freetext" href="http://EmSai.net/">http://EmSai.net/</a>
</pre>
</body>
</html>