- From: Ian Hickson <ian@hixie.ch>
- Date: Sat, 31 Dec 2005 01:03:18 +0000 (UTC)
On Tue, 20 Dec 2005, Sander Tekelenburg wrote: > > Maybe I'm misunderstanding what you mean, but it seems to me that the > only way server-side includes can help with this in in the sense of > authors not having to define the same content twice. The user-agent will > still *receive* it twice, resulting in LINK capable browsers wasting > space by repeating the content in-body. I can't speak for Alexey, but > *that* is the repetition problem I am referring to. > > FWIW, my aim is to get at a place where "navigation menus" can be > authored in such a way that user-agents won't have to receive it twice > and can (if they want) display it outside of the canvas in a way that > works the same across sites, thus making navigation more recognisable > and therefore easier. If that can be achieved without LINK that's > perfectly fine with me. It's not LINK itself that I care about. If we're trying to solve the problem of _sending_ the data twice, that is easily solvable, by using rel="" on <a> elements instead of <link> elements. If we're trying to solve the "problem" of displaying the link navigation twice (once in the page and once in the browser UI) then I'm not convinced that's a problem, or that we should be solving it. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 30 December 2005 17:03:18 UTC