diff options
| author | Jacob Nevins <jacobn@chiark.greenend.org.uk> | 2007-01-28 17:16:48 +0000 |
|---|---|---|
| committer | Jacob Nevins <jacobn@chiark.greenend.org.uk> | 2007-01-28 17:16:48 +0000 |
| commit | e02852ebbc72fa47fe4578eb1a7846dd24af2720 (patch) | |
| tree | 3f632d37e4a67b168cb62938620ed05214d4c4a0 /malloc.c | |
| parent | 15e205a0b12194a79eda05b283b88e352166d631 (diff) | |
| download | halibut-e02852ebbc72fa47fe4578eb1a7846dd24af2720.zip halibut-e02852ebbc72fa47fe4578eb1a7846dd24af2720.tar.gz halibut-e02852ebbc72fa47fe4578eb1a7846dd24af2720.tar.bz2 halibut-e02852ebbc72fa47fe4578eb1a7846dd24af2720.tar.xz | |
Minimal support for <LINK REL="next"> etc machine-readable navigation links.
Off by default for now, but I don't intend that it should stay this way; they
seem useful and harmless. I just want to check a few more browsers to ensure
they don't do anything obnoxious with them.
So far I've only seen lynx and links do something with them (provide toolbars).
iCab and some Mozilla derivatives/extensions are also alleged to do this; Opera
is said to allow PgDn type browsing through the entire set of pages; and
Mozilla is rumoured to use the "next" link for prefetching.
[originally from svn r7177]
Diffstat (limited to 'malloc.c')
0 files changed, 0 insertions, 0 deletions