- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 7 Jan 2003 03:02:54 +0000 (GMT)
- To: Herr Christian Wolfgang Hujer <Christian.Hujer@itcqis.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Tue, 7 Jan 2003, Herr Christian Wolfgang Hujer wrote: > > I think a href has a behaviour that effectivly consists of three steps: > The behaviour requesting the object from the user agent. (That makes it > possible for a spider or a tabbed browser to thread / tab) > The user agent creating and delivering the object. > The behaviour invoking the desired method or altering the desired attributes > of that object. I would say that's its semantics. The _behaviour_ of an <a href> is typically more along the lines of: event handlers: on click, run activation function. href property: resolve the value of the "href" attribute relative to the element's base URI. style: underline, colour based on visited state. activation function: change "location.href" to the value of the "href" property. But it varies. (The two examples I gave where lynx, a Web browser that at least in one version only had keyboard interaction for links, and Qube, another Web browser that in one version only had mouse support for links.) -- Ian Hickson )\._.,--....,'``. fL "meow" /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 6 January 2003 22:02:56 UTC