Posted by Chris F.A. Johnson on 08/20/06 10:28

On 2006-08-20, Jukka K. Korpela wrote:
> Chris F.A. Johnson <cfajohnson@gmail.com> scripsit:
>
>> What doesn't work? Show the code you use. E.g.:
>>
>> <a href="http://www.url.com/page.html#something">Something</a>
>
> We actually need the real URL of the page where the link is and information
> about which link there is meant. That way we can also access the real URL of
> the linked page, where the problem probably is. Oh, and _please_ stop using
> domain names like www.url.com if you don't _really_ mean the real domain
> name! There's a good old convention (documented in RFC 2142) of using the
> top-level pseudo-domain "example" (e.g., www.foo.example) or the
> second-level pseudo-domain "example.com" (e.g., www.example.com) for dummy
> domain names in examples. They are guaranteed to be and remain dummy (never
> actually assigned).

Quite right. My apologies.

> However, consider first whether it is a good idea to jump into the middle of
> a page with a link. I say it often is, but Jakob Nielsen seems to have a
> different view, and he mostly knows usability better than I do; see
> http://www.useit.com/alertbox/within_page_links.html

Jakob Nielsen needs to be take with a pound of salt. He makes some
very good observations intermingled with lots of nonsense.

--
Chris F.A. Johnson <http://cfaj.freeshell.org>
===================================================================
Author:
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)

[Back to original message]